-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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] fixup pkgconfig #18123
[openexr] fixup pkgconfig #18123
Conversation
Unfortunately, it is no enough. For debug, libraries are build with a
Fortunately, given the |
Many thanks for catching @dg0yt, I appreciate you looking over this. Any objection to instead simply setting CMAKE_DEBUG_POSTFIX to the empty string as in the commit I just added? |
(Note https://github.com/AcademySoftwareFoundation/openexr/blob/master/cmake/OpenEXRSetup.cmake#L72 so it really needs to be explicitly set to the empty string.) |
IMO it is fine, as long as library names match exported cmake and pkgconfig configuration. It seems hardly possibly to use these libs correctly without exported configuration. (I will know more when I add openexr support to port gdal.) However, vcpkg policy is to not rename binaries outside the names given by upstream. Decision left to approvers. |
Thanks, and sure, I asked explicitly because of that policy. Using an upstream configurable setting to fix issues with the upstream exported .pc configuration would seem within reasonable boundaries to me and guarantees all configurations (cmake, pkgconfig) remain in sync; it's not like renaming the libraries post-installation. But if it's not ok, I'd be happy to try to fix the openexr .pc generation with a patch that can be upstreamed. However, I really rather go for the currently proposed and much simpler solution, not requiring any special case regexp-ing of the .pc files, and not requiring any upstreamable patches. |
Policy is policy. You don't know if a downstream port has a custom |
Sure. I've posted a patch upstream. |
There's some non-trivial discussion upstream on how best to fix this. I'll put this back on draft until the outcome of that discussion is clear, so I can add the final upstream patch. |
Please ping me if this PR is ready for review. |
@JackBoosY Thanks, your message was perfectly timed: upstream just merged the patch! It's ready now for review. |
LGTM, thanks @mcmtroffaes :) |
What does your PR fix?
The generated .pc file for openexr contains an absolute path. This PR fixes that.
Which triplets are supported/not supported? Have you updated the CI baseline?
No changes.
Does your PR follow the maintainer guide?
Yes, to the best of my knowledge.
If you have added/updated a port: Have you run
./vcpkg x-add-version --all
and committed the result?Yes.