Using Conan 2.0, invoke via conan install or CMake | Together C & C++ | Page 1

paper harbor May 25, 2024, 2:32 PM

#

So I'm currently testing out switching from vcpkg to Conan 2.0 and I'm wondering if its better practice to build using conan install ... or using CMake via cmake-conan (https://github.com/conan-io/cmake-conan)

GitHub

GitHub - conan-io/cmake-conan: CMake wrapper for conan C and C++ pa...

CMake wrapper for conan C and C++ package manager. Contribute to conan-io/cmake-conan development by creating an account on GitHub.

cunning saffronBOT May 25, 2024, 2:32 PM

#

When your question is answered use !solved to mark the question as resolved.

Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question use !howto ask.

slim plume May 25, 2024, 4:38 PM

#

so, the cmake-conan stuff is not the officially preferred or endorsed way of using conan,
but I'd say it depends on your project

#

if you are only trying to consume packages from conan, not author a conan package yourself, then I do prefer to just use the conan_provider.cmake so cmake can drive my build, and in turn IDEs with cmake integration can drive my build, and I don't need to run any manual install steps when I want to switch configs etc.

#

however, I've had to hack around in the conan_provider.cmake a bit in the past because the auto detection is influenced by your user-wide conan config and default profile, and goes kind of haywire if you try to use both MSVC and MinGW toolchains on windows, where the default profile will contain mutually exclusive options either way you go

paper harbor May 25, 2024, 4:44 PM

#

so my c++ project is actually a python extension module that is used from python so would using conan make it any easier over something like vcpkg

slim plume May 25, 2024, 4:47 PM

#

not sure

paper harbor May 25, 2024, 7:43 PM

#

!solved

#Using Conan 2.0, invoke via conan install or CMake