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.

Sign up for GitHub

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

add announcement for moving to vc142 #1810

Merged
merged 4 commits into from
Aug 11, 2022
Merged

add announcement for moving to vc142 #1810

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
faec28e
add announcement for moving to vc142
h-vetinari Aug 10, 2022
70378e9
Update src/user/announcements.rst
h-vetinari Aug 11, 2022
0d92996
add link to pinning PR
h-vetinari Aug 11, 2022
fda0b08
add some useful words
h-vetinari Aug 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions src/user/announcements.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,23 @@ Our announcements are published to an RSS feed `here <https://conda-forge.org/do
----


2022-08-11: Moving to Visual Studio toolchain vc142
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Microsoft has deprecated the Visual Studio (VS) 2017 compiler and removed it
from all the CI they control (notably Azure Pipelines & Github Actions).
This means that the default toolchain (== C++ compiler, linker, standard
libraries, and related utilities) of that VS version - vc141 - is getting less
and less use in upstream libraries (because their public CI doesn't use it
anymore without a lot of fiddling), and therefore support for it is bitrotting
h-vetinari marked this conversation as resolved.
Show resolved Hide resolved
at an accelerating pace. We are therefore planning to move our toolchain on
windows to vc142 (the default in VS2019) in two weeks, on 2022-08-25.

This will not affect you as a general user of conda-forge packages on windows;
the only impact is that if you are locally compiling against artefacts produced
by conda-forge and are still using VS2017 yourself, you will need to upgrade your
compiler (VS2019 is a drop-in & ABI-compatible).
h-vetinari marked this conversation as resolved.
Show resolved Hide resolved

2022-07-22: Azure OSX VM Image Bumped to Version 11
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Expand Down