CXX-2973 add pkg-config test coverage using pkgconf #1546
Merged
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.
Suggestion cannot be applied right now. Please check back later.
Resolves CXX-2973 by using
pkgconf(obtained viauv tool) on Windows distros as followup to #1536.Per pkgconf docs:
and per Wikipedia:
The
pkgconfproject is actively maintained, with its latest release being 2.5.1 on June 2025. In contrast, the PyPI package for pkg-config has not been updated since July 2021. The pkg-config project itself has not seen any activity since January 2021, with the last stable release being 0.29.2 on March 2017. Therefore, this PR proposes adoptingpkgconfas successor topkg-config.Following #1428, the
pkgconfapplication can be easily obtained usinguv tool installviainstall-build-tools.sh. Note thepkgconfpackage also provides apkg-configbinary alongside thepkgconfbinary. Therefore, existing calls topkg-configdo not need to be changed.