-
Notifications
You must be signed in to change notification settings - Fork 980
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
[question] Conan 2.x Transition - MSVC Compiler Version #17118
Comments
After some more digging and looking at the settings.yml reference, I added the following to our global.conf: That got me past the Thanks |
Sorry, do you mean that you are still using VS 2010 (compiler.version=160)? Conan 2 defined a base minimum of VS 2015 (compiler.version=190) with CMake 3.15. |
Yes, correct - our Windows build machines are currently using VS 2010. Thank you for the background on what versions are supported with Conan 2. I am going to attempt getting MSBuild 2022 installed and working for all of our Windows build machines in hopes of avoiding any conanfile.py hacking to make VS 2010 work. |
@memsharded, I installed the latest "Build Tools for Visual Studio 2022" distribution. The compiler version is reported as:
Looking at the settings.yml documentation it looks like I should have Could you provide some guidance as to the correct configuration to use given the compiler version above, please? Thanks! |
The recommendation would be to use |
Yes, supporting VS2010 might be a bit of an effort, because both Conan client, but also recipes in ConanCenter do not generally provide support for it. In the case above it seems the |
What is your question?
Transitioning my company from Conan 1.x to 2.x and after successfully building packages with Linux-based profiles, I ran into an issue with our single Windows profile.
Question: What is required to add a new MSVC compiler version to settings.yml so the generator helpers (e.g. Autotools*) can be used?
We are using MSVC compiler version 16.0.40219.1 which translates to 160 per the Microsoft guidance. Originally I had simply updated my settings.yml to include version 160:
Our Windows profile looks like:
While some packages built fine with the Windows profile, I ran into an issue with the OpenSSL package in
generate()
. I originally thought it was specific to the package but now believe it's a general problem related to the MSVC version I added. When usingAutotoolsToolchain.generate()
I get an error:After some debug I found the '160' was referring to the new MSVC version I had added. So, it feels like there is more to adding an allowed version than the simple settings.yml update I did.
Any help would be greatly appreciated.
Thanks
Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: