-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[liblzma] Generally fix output name #20751
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
I had to revise the PR after more testing, and came to a more general fix. I update the initial post. Sorry for the inconvenience. |
target_sources(liblzma PRIVATE src/liblzma/liblzma_w32res.rc) | ||
target_include_directories(liblzma PRIVATE windows/vs2019) | ||
# It's liblzma.so or liblzma.dll, not libliblzma.so or lzma.dll. | ||
# Avoid the name lzma.dll because it would conflict with LZMA SDK. |
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.
The name lzma.dll
wasn't and isn't avoided in vcpkg so far. If desired, we need to set property RUNTIME_OUTPUT_NAME
to liblzma
(for win32 but not mingw).
All checks green. |
Thanks for the fixes! |
What does your PR fix?
This PR fixes liblzma to not mess with the platform's prefix but simply always use the
lzma
"namespec" that matches-llzma[d]
as used in the .pc file. This fixes library name issues on mingw. The change is complemented by tightening thefind_
calls in the exported cmake configuration.Another change fixes the warning about the unused
CMAKE_DEBUG_POSTFIX
variable.Which triplets are supported/not supported? Have you updated the CI baseline?
unchanged
Does your PR follow the maintainer guide?
yes
If you have added/updated a port: Have you run
./vcpkg x-add-version --all
and committed the result?yes