[szip, hdf5] Fix mingw import lib names, control linkage#17941
[szip, hdf5] Fix mingw import lib names, control linkage#17941strega-nil-ms merged 20 commits intomicrosoft:masterfrom
Conversation
|
When building |
I will take a look. I even did builds with hdf5 but this didn't show up. Basically, for triplets with dynamic linkage,
I will push the hdf5 changes on top of this PR. I need to fix mingw and pc files. |
|
This is now extended to hdf5, and fixes hdf5 build failures with mingw (but no hdf5 cross-builds).
|
longnguyen2004
left a comment
There was a problem hiding this comment.
Thanks for making this PR! I always felt my approach was wrong, since mingw import libs aren't supposed to have the extension .lib, so I'm very thankful that a proper fix is coming.
|
@longnguyen2004 Do you have any suggestions? |
|
LGTM |
|
"-lszip-static" still seems to slip into the linux hdf5 pc files. I need to verify this again. |
|
Turned out that the repeated |
|
Ping. |
|
LGTM, thanks @dg0yt :) |
What does your PR fix?
This PR:
...dll.a), resolving the "Could not find proper second linker member" error which was the reason for settingVCPKG_POLICY_SKIP_ARCHITECTURE_CHECKfor szip in the mingw triplets,It also changes the version format from version-string "2.1.1-6" to version "2.1.1" port-version 7.
Which triplets are supported/not supported? Have you updated the CI baseline?
all, no
Does your PR follow the maintainer guide?
yes
Even with this PR, the static builds on Windows have an unusual
libprefix (libszip.lib for MSVC, liblibszip.a for mingw). It could be changed now, when the static lib is no longer build in additon to the dynamic lib.liblibszip.aliblibszip_D.alibszip.dll.alibszip_D.dll.a*) Before this PR: static lib was also built