libcurl.pc: Merge Libs.private into Libs for static-only builds #5373
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
A project being built entirely statically will call pkg-config with
--static
, which utilises theLibs.private
field. Conversely it will not use--static
when not being built entirely statically, even if there is only a static build of libcurl available. This will most likely cause the build to fail due to underlinking unless we merge theLibs
fields.Consider that this is what the Meson build system does when it generates pkg-config files.
I have also reflected this in the
--libs
argument of curl-config even thoughREQUIRE_LIB_DEPS
always seems to beyes
anyway.