Gerard

@memsharded, thanks for your response. In this case the lockfile generated by the parent job is fully specified; each package in the dependency graph has the package revision filled out...

@memsharded - I saw you mention at the beginning of the year that the plugins were not getting attention due to Conan 2.0. The inability to use the Conan plugin...

Hello @czoido, thanks for your response. For question 1, your guidance helped a lot - I updated the producer and consumer conanfile.py files as directed in that link and all...

Following up, I started over (recreated the CLion toolchain and CLion CMake profile) with the Conan 1.x/Conan Plugin 1.x pre-existing CMake profile and now it is correctly finding header files...

Closing this ticket as the original questions are resolved. Opening new tickets for some new issues I see with multiple profiles. Thank you!

Hello, @czoido - thanks for your response. > If you want to depend on the presets produced by Conan I'm just looking for the best/right solution - no preference for...

After some more digging and looking at the [settings.yml reference](https://docs.conan.io/2/reference/config_files/settings.html), I added the following to our global.conf: `tools.microsoft.msbuild:vs_version = 10` That got me past the `AutotoolsToolchain.generate()` error. I'm assuming some...

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...

@memsharded, I installed the latest "Build Tools for Visual Studio 2022" distribution. The compiler version is reported as: `Microsoft (R) C/C++ Optimizing Compiler Version 19.41.34120 for x64` Looking at the...

I have successfully gotten the various packages we build for Windows targets working with the latest MSBuild 2022 release. Thanks again for all your help, @memsharded! Closing.