-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[develop2] Variable "CONAN_<PackageName>_ROOT" not set anymore #562
Comments
Hi @jacobalexis Thanks for your report. So maybe we should move the issue to the conan repo? The idea is that you should move first the recipes to be Conan 2.0 compatible, with the latest Conan 1.X and using the modern generators. |
I understand, thanks for your quick answer.
We are in the process of migrating our libs from Conan 1.X to Conan 2.0 but some Conan 2.0 libs from conancenter do not seem to have been migrated, as they are raising warnings, cf below:
Do we need to move those recipes to be Conan 2.0 compatible as well, temporarily within our own private conan center? |
Greetings :)
For the migration of a C++ project from Conan 1.X to Conan 2.0, I was considering the latest version of Conan_cmake on develop2. Here is the issue that I am facing currently:
So far, we actually use several macros to keep track of each library folder, including 3rd parties That use case was satisfied by variable
CONAN_<PackageName>_ROOT
, which was set by callingconan_cmake_run
if I understand it correctly.The new behavior gets rid of any conan function call in the project itself. Can there still be a way to fetch the path of each library folder that is called by the conan install? What would you advise?
Many thanks in advance for your answer,
Alexis Jacob
The text was updated successfully, but these errors were encountered: