[question] moving legacy vars in CMakeConfigDeps #18860

[maitrey]

What is your question?

Dear Conan Folks,

I had a look to the change:
https://github.com/conan-io/conan/pull/18860/changes#diff-9702be6f4b6f8f16c94336e99f3c6188493450fbe087b4656847ab9a19902581.
I use cmake-3.31.6.
I am not sure what changes should I expect. When I compare the generator files from conan-2.11.0 to 2.24.0 I see that for the -release--.data.cmake the set _PACKAGE_FOLDER_RELEASE has ${CMAKE_CURRENT_LIST_DIR}/../../../full_deploy/host instead of hard coded paths to the package.

Could you please help , Also I use conan build and conan export-pkg.

Thanks in advance!
Br,
Maitrey

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide

[memsharded]

Hi @maitrey

Thanks for your question.

I am not sure what you mean.

That is the CMakeConfigDeps generator. A new one, not the CMakeDeps one. If you are using CMakeDeps, nothing changes.

If you want to try the CMakeConfigDeps new generator, released in Conan 2.25, this summarizes the differences with respect to the CMakeDeps, check https://docs.conan.io/2/reference/tools/cmake/cmakeconfigdeps.html -> Improvements over CMakeDeps. It uses a completely new structure, new targets, new files, everything is new. Still, from the point of view of the consumer, the find_package(), target_link_libraries() should be the same.

[maitrey]

I read the documentation about CMakeConfigDeps after you mentioned above, Sorry.
Feature: Allow profile composition while using conan runners. #18534
Could you please explain what could be the use-case to create a profile dynamically?

[memsharded]

That is completely unrelated to the original ticket, related to the "runners" feature: https://docs.conan.io/2/reference/runners.html#runners

But not related to CMakeConfigDeps at all.

Also, creating profiles dynamically is not something only for the "runners". Actually, I am not sure what you mean by "creating profiles dynamically", or where it comes from.

If the original question about CMakeConfigDeps is solved, it would be better to close this ticket, and open a new ticket.
Better than referring to a maintainers PRs, please try to refer to user stories, what are you trying to do, what fails, etc. Use exact wording, and exact commands, detailed conanfiles, etc, to express your questions, your intentions. Refer better to the Conan docs than to the code.

Thanks for the feedback.

[maitrey]

Sorry for abusing the same github issue for asking two questions.
I do not wish to switch to CMakeConfigDeps in production for now.
And went to the next feature from the changelog that I had listed as interesting for us.
You are absolutely right in assuming that I read the PRs and not the documentation and therefore caused confusion too.
I will go through the documentation and ask any further questions on a seperate issue.
This Issue can be closed.

[memsharded]

Sorry for abusing the same github issue for asking two questions.

No problem, just confusing to follow.

I do not wish to switch to CMakeConfigDeps in production for now.

Sounds good, no need to rush if CMakeDeps is working fine for you. You have the tools.cmake.cmakedeps:new=will_break_next configuration to allow doing testing of the new generator without needing to modify recipes.

Thanks for the feedback, closing the issue.