Luis Caro Campos

As for the `cmake_minimum_required()` - indeed this will be a problem with CMake 3.28 if the different subdirectories have a call to that function for a version earlier than 3.28,...

Hi @simonimpey - thank you for reporting this issue. The new integration (develop2) currently expects this information to be provided in the `default` profile (and if the default profile does...

Hi @simonimpey - I see, this is probably relevant if CMake is being run with Visual Studio. I should be able to reproduce this, will give this is a go...

Hi @simonimpey - I've tried to reproduce this on my end, but have been unable to. If I open the project directly from Visual Studio (where the VS IDE invokes...

> I can confirm that this only happens if you run it via the VSCode integration of CMake. HI @fklebert - thank you for reporting this as well. This seems...

HI @fklebert - thank you for providing the log. In this case I have a strong suspicion that the `CC` and `CXX` environment variables are set to point to `cl.exe`...

> I think the original cause of the issue was running conan for the first time and auto detecting the profile from within whatever environment VS uses when processing CMakeLists...

Hi @pwqbot - thank you for trying out the new integration and reporting this issue. The error you are seeing is related to one of the current limitations mentioned in...

we are not currently considering having Conan generate `conan_toolchain.cmake` (`CMakeToolchain`). That needs to provided before the first invocation of cmake configuration, and as such, Conan would need to be invoked...

> Since Conan Team insisted that we should include the `conan_toolchain.cmake` file in the the following previous issues: > > * [[feature] Add `IMPORTED_LOCATION_` properties for Imported Targets created by...