Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Appveyor #25

Merged
merged 15 commits into from
Aug 20, 2018
Merged

Configure Appveyor #25

merged 15 commits into from
Aug 20, 2018

Conversation

benbovy
Copy link
Member

@benbovy benbovy commented Aug 17, 2018

TODO:

  • add badge in README
  • add Python to test matrix (test only for VS2015, which is used by conda for Python 3.5+)

Maybe for later: google-test is installed using conda (built in release mode I guess), which probably causes the MSVC linking error if tests are not built in release mode too. So we build here in release mode. It's probably not the best solution, but at least there is no error. An alternative could be building google-test from source in debug mode? Or maybe the real issue is static vs. dynamic linking to google-test?

@benbovy
Copy link
Member Author

benbovy commented Aug 17, 2018

Conda forge recently dropped support for building for Windows 32 bits. As a result, xtensor recent versions are not available anymore in the conda-forge channel for win32 (although it seems to be still available in the Quanstack channel).

Fastscapelib will certainly be packaged using conda forge, so tests for win32 are disabled for now. We'll see later if we really need to support it.

@benbovy benbovy merged commit d977000 into master Aug 20, 2018
@benbovy benbovy deleted the config-appveyor branch August 22, 2018 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant