-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
openexr 2.x: avoid conflict in PkgConfigDeps #24563
openexr 2.x: avoid conflict in PkgConfigDeps #24563
Conversation
PkgConfigDeps generate OpenEXR.pc for openexr_ilmimf component , while an unwanted openexr.pc file is generated by default by "global" component. To avoid conflict on case-insensitive file systems like Windows, we enforce an another custom pkg_config_name for this global component.
Conan v1 pipeline ✔️All green in build 1 (
Conan v2 pipeline ✔️
All green in build 1 ( |
Hooks produced the following warnings for commit 7c23bbdopenexr/2.5.9@#250b6c8e60b746b6e75734373ed98754
openexr/2.4.0@#be0d95e9c8ba3901fa5d5354961a68b8
openexr/2.5.7@#191290b5cb7da90a05ed351fae29d9c4
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Works with my example. LGTM. Thanks! |
Summary
Changes to recipe: openexr/2.x
Motivation
Avoid conflict between files generated by
PkgConfigDeps
for openexr 2.x on case-insensitive file systems.closes #24559
Details
PkgConfigDeps
generateOpenEXR.pc
file foropenexr_ilmimf
component , while an unwantedopenexr.pc
file is generated by default for the "global" component. To avoid conflict on case-insensitive file systems like Windows, we enforce an another custompkg_config_name
for this global component.