klionmeister.blogg.se - Clion cannot find any cmake profile

Clion cannot find any cmake profile install#
Clion cannot find any cmake profile software#
Clion cannot find any cmake profile code#

This is kind of standard in other languages, you clone the project, then do npm install, or whatever to fetch dependencies.

Clion cannot find any cmake profile install#

Users get a bit used to do conan install when they clone a project with Conan dependencies.

So the only possibilities that we see moving forward are: But more importantly because the integration relies on generating CMake toolchain.cmake files and CMakePresets.json files, and has CMake cannot get these files after it is launched, read them from CMakeLists.txt, this is an unsolvable problem. You can't have both, it is impossible to have a transparent integration, and also have CMake call automatically Conan, because that highly pollutes the CMakeLists.txt files. These integrations are more powerful, flexible and complete than the previous ones, so we are happy with them, and they are the ones that are moving as the only ones in 2.0.īut this introduced a chicken-and-egg problem. The pressure continued to produce CMakePresets files too. That was the origin of CMakeToolchain and CMakeDeps. Relatively well, means that it has its issues, for example, need to deal with multi-configuration projects, installing Debug/Release configurations in one pass, further polluting every CMakeLists.txt that relies on it.īut on the other hand, we got a huge pressure to implement a "transparent" integration, that is, one that didn't need to modify anything in your CMakeLists.txt at all. Even if I didn't love this integration, it worked relatively well with the previous CMake integrations ( cmake generator). That project was born by the desire of some users to run just cmake, and let it call conan automatically. Hi guess that you are talking about the integration, but you are concerned about its limitations. Is there a seamless integration of Conan into CMake that doesn't require me to call Conan before I call CMake? Is my expectation, about what Conan should be used for / should be capable of, somehow wrong? Is there an example project accessible, that integrates CMake and Conan). But in this case, the required toolchain file has to exist already before I call CMake (and as there is a chance, that the project has to be cross build in the future, we probably are going to use the tool chain feature of CMake on our own).

The preferred method to integrate both, seems to be the CMakeToolchain integration. And of cause, if our Conan configuration changes (which simply can happen, by switching the branch), I don't want to explicitly run Conan, but use CMake to detect the required update.

Clion cannot find any cmake profile software#

I had the dream, that I could simply checkout our sources and use CMake to configure and build the software and that Conan is integrated into the CMake build, so that it gets called to determine the required include and library paths and of cause, to install missing libraries / dependencies. Now, I would like to integrate Conan into CMake.

Now I have a pretty large command line for installing every configuration, which I probably could shorten a little bit, by using profiles and a large command line for the CMake configuration, which I can shorten largely by using presets. So far, I was able to configure Conan to install our dependencies (using the 3 configurations above) and to build the software and their tests. We have 3 different build configurations (gcc-debug, gcc-release, clang-debug). I've convinced my team to use Conan to install the dependencies and thus to codify our dependency and to pin the exact version, we are using with a specific version of our own project. The exact versions of the installed dependencies where more or less random and depended on the time of execution.

Up to now, we use a shell script to install the dependencies in docker.

Clion cannot find any cmake profile code#

Nevertheless, the code base has some dependencies on external libraries and these external libraries have their dependencies on their own. I'm currently working on a project with a small team working on a relative small code base.