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

appveyor and vs2015 deprecation #1012

Closed
6 tasks done
beckermr opened this issue Mar 24, 2020 · 7 comments
Closed
6 tasks done

appveyor and vs2015 deprecation #1012

beckermr opened this issue Mar 24, 2020 · 7 comments

Comments

@beckermr
Copy link
Member

beckermr commented Mar 24, 2020

To Do

Feedstock Census

See notes here: https://hackmd.io/@beckermr/rJPw0tnDL/edit

@beckermr beckermr pinned this issue Mar 24, 2020
@beckermr beckermr changed the title appveyor deprecation appveyor and vs2015 deprecation Mar 25, 2020
@isuruf
Copy link
Member

isuruf commented Mar 25, 2020

From the announcements page

We are formally deprecating vs2015 in two weeks on 2020-04-07 and will move to vs2017. This change will enable us to support the usage of msbuild on Azure for the win platform and will provide additional support for C++. Most packages built with vs2015 can be linked with vs2017 toolchain (but not vice-versa). An exception is static libraries compiled with whole program optimization (/GL flag) which may be incompatible with the vs2017 toolchain. These static libraries will need to be rebuilt using vs2017.

@isuruf
Copy link
Member

isuruf commented Mar 25, 2020

@xhochy, we added /GL by default to CFLAGS env variable in vs2015_win-64 package. So some static libraries might have been created with /GL inadvertently.

@beckermr
Copy link
Member Author

I'm seeing this conda-build warning a lot:

WARNING (lz4-c,Library\bin\liblz4.dll): Needed DSO C:\Windows\System32\VCRUNTIME140.dll not found in any CDT/compiler package, nor the whitelist?!

any ideas anyone?

cc @conda-forge/core @isuruf

@beckermr
Copy link
Member Author

beckermr commented Mar 31, 2020

Besides the warning above, the new compiler appears to be working. It has built lz4-c, mpfr, mpc, m4ri and libdb.

@isuruf
Copy link
Member

isuruf commented Mar 31, 2020

any ideas anyone?

That's a conda-build issue. conda-build checking is case sensitive, when it shouldn't be.

@beckermr
Copy link
Member Author

I think overall the new compiler is good to go.

@beckermr beckermr unpinned this issue Apr 14, 2020
@beckermr
Copy link
Member Author

All of the work here is done! Closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants