Open kmilos opened 1 month ago
@kmilos instead of pkgconf if pkg-config were used, wouldn't this change break static builds as cflags.private is not supported by later.
Possibly, in theory... However, you'd only add these on Windows when building a shared lib (or both shared + static), and all "major" Windows dev frameworks I'm aware of (vcpkg, MSYS2 MinGW, and Cygwin, even Conan) ship only pkgconf
.
So it's up to you - either do this and wait for (unlikely?) breakage reports from some more exotic build environments on Windows, or leave it out and let the packagers patch it on their own accord...
Although not strictly necessary and functions without so far, the
-DUHDR_USING_SHARED_LIBRARY
hint might help the linker generate more optimal output on Windows.When building a shared lib on Windows (any compiler), the resulting .pc file should look like:
P.S. At least on MSYS2 (using
pkgconf
rather thanpkg-config
), the same .pc file can also support both shared and static libs by also adding the (undocumented)as well.
See e.g. https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-libdeflate/002-pkg-config.patch
Edit: I see that vcpkg also ships
pkgconf
rather thanpkg-config
, so should work out there as well.