-
Notifications
You must be signed in to change notification settings - Fork 985
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
[feature] Backport new msvc compiler settings to old build helpers and generators #10364
Comments
It was never intended to backport the From now on, changes in the build system integrations will only be done for important bugs, but not new features like supporting the new |
Therefore I think it is a bad user experience to create profile with |
Let's fix the compiler=msvc => compiler=Visual Studio auto-detect until ConanCenter catches up supporting it. |
#10457 switched to detect VS 17 instead of msvc 193 for VS 2022 |
conan-center-index cannot ensure proper support of the new compiler
msvc
insettings.yml
since all CCI recipes rely either oncmake
+ oldCMake
helper, or things likeAutoToolsBuildEnvironment
/MSBuild
/VisualStudioBuildEnvironment
/Meson
helpers.I've tested to support
libsodium
for example (conan-io/conan-center-index#8957).It builds with these 2 profiles:
But the second one reports some linking incoherency in CMake based test_package (and not the first one):
So I guess there is some magic missing for this new compiler in old helpers or generators.
In this example I think there are 2 issues:
LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs; use /NODEFAULTLIB:library
(I guess thatMSBuild
has not properly honoredcompiler.runtime
).ignoring unknown option '/dynamic'
The text was updated successfully, but these errors were encountered: