Skip to content
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

Discuss future approach for cpp_info.names and cpp_info.filenames #8600

Closed
memsharded opened this issue Mar 4, 2021 · 3 comments
Closed
Assignees
Milestone

Comments

@memsharded
Copy link
Member

Coming from #8568:

  • The cpp_info.names["cmake_find_package_multi"] strategy for custom generators behaviors seem too specific
  • Consider using something more generic like cmake (when this doesn't break for current cmake generator)
  • Or a conceptual name: cmake_targets_names, that could be exploited by different generators
@memsharded memsharded added this to the 1.35 milestone Mar 4, 2021
@memsharded
Copy link
Member Author

Related #7661

@lasote
Copy link
Contributor

lasote commented Mar 25, 2021

Note: It is not strictly related to this issue but as an observation, for the CMakeDeps only the cpp_info.filenames field affects to the name of the xxx-config.cmake file, it doesn't default to the self.cpp_info.names like the older generators.

@memsharded
Copy link
Member Author

Closed by #8727

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants