Mateusz Pusz
Mateusz Pusz
> So talking more abstractly, adding global configuration for things that are exclusively local, is a common source of misunderstandings and issues. That is a pity because I would love...
> When you are working on a project you have a few files: >- CMakeLists.txt - conanfile.py (it defines to generate for example ConanPresets.json) - CMakeUserPresets.json that includes ConanPresets.json I...
> It would be good if you could provide us with an example CMakeUserPresets.json that does this inclusion so that the issue can be better illustrated Imagine that I want...
In general, CMake presets suck when you want to compose something fancier from several presets 😢 There really should be some command that would allow you to combine lists of...
Anyway, this feature is not that important to spend hours discussing it. I thought it might be a simple and nice addition, but if you find it controversial, then you...
Maybe another way around? Maybe there should be a config option similar to `tools.cmake.cmaketoolchain:user_toolchain:` but for presets? However, this one should be more complicated. It should contain: - user presets...
Please note that the latest VSCode seems to support workflow presets as well. It would be great if Conan could automatically create a preset like the below: ```json { "version":...
@thorntonryan, does this workaround still work for you with Conan 2.0? I am getting "No CMAKE_CXX_COMPILER could be found." which means that the VSCode does not load `vcvars`.
Thanks! By adding the following: ```diff { "version": 3, "vendor": { "conan": {} }, "cmakeMinimumRequired": { "major": 3, "minor": 15, "patch": 0 }, "configurePresets": [ { "name": "conan-msvc-193", "displayName": "'conan-msvc-193'...
Right! It should be the case. But Conan generates different target types and more of them than the regular CMake installation process. It might be an issue. BTW, recently I...