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

[bug] Allow not propagating component requirements usage to consumers #12965

Closed
memsharded opened this issue Jan 24, 2023 · 0 comments · Fixed by #12966
Closed

[bug] Allow not propagating component requirements usage to consumers #12965

memsharded opened this issue Jan 24, 2023 · 0 comments · Fixed by #12966
Assignees
Labels
Milestone

Comments

@memsharded
Copy link
Member

Environment details

All versions, compilers and OSs

Steps to reproduce

  1. Create a recipe "wayland" with 2 components: 1 executable "wayland-scanner" and 1 lib "waylandlib"
  2. Executable wayland-scanner depends on libxml2 and expat to be built
  3. We don't want to propagate libxml2 and expat to consumers that will tool_require wayland-scanner executable,so we dont add it to package_info()

that will raise, a Conan protection that forces every pkg dependency to have components propagated.
Relax that assumption so this is allowed.

Logs

No response

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

Successfully merging a pull request may close this issue.

1 participant