proposal for loading conan_cmakedeps_paths.cmake#674
Conversation
|
cc @jjcasmar |
|
Hi, maybe the following question is more related to the CMakeConfigDeps-generator in general than the cmake-conan-wrapper, but I came across it while testing the I have put all files in a repository (https://github.com/ottmar-zittlau/conan-cmake-question) in case you'd like to follow my steps. I have created a small (interface) library (in repo: test_lib) that only contains a header file. This library is consumed by an executable (in repo: main_exe) by: If I follow the conventional approach (conan install + generated presets) everything works. cmake complains that target My build folder contains I'm pretty confident that cmake reads this file (I printed the variable I was comparing the variables set in How can I make this work? Do I maybe need to add something else to my library's Thanks in advance and best regards |
|
Thanks for the feedback. We have just released |
|
@memsharded Thanks a lot! It's not an urgent issue for me. |
|
I am going to merge and close this PR.
|
... and instead print a warning. This is what the upstream conan-cmake does. Also mention the CMakeConfigDeps generator. See conan-io/cmake-conan#674 for details. Fixes: QTCREATORBUG-34015 Change-Id: I52b9c0b19bead3c1f71024829239cc2582eba519 Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
After conan-io/conan#17561
This PR does:
CMakeConfigDeps, explicitlyCMakeConfigDepsCMakeConfigDepsCMakeDeps. User conanfiles should define the generator. The warning has been there for a long time alreadyCMakeConfigDepsThis doesn't really change or break users with
CMakeDepsin their conanfiles.