Skip to content
package compiler and linker metadata toolkit
C Shell M4 Makefile Meson
Branch: master
Clone or download

Latest commit


Type Name Latest commit message Commit time
Failed to load latest commit information.
.builds builds: add fedora meson build Jul 12, 2019
cli main: extend copyright statement to 2020 in --about May 26, 2020
doc doc: update fragment API docs Jan 14, 2019
libpkgconf meson: remove some autotools cruft Jun 3, 2020
m4 Only add warnings and std flags if supported by compiler (autoconf) (#… Sep 26, 2017
man cli: add support for PKG_CONFIG_MSVC_SYNTAX env variable May 24, 2020
tests Revert "tests: remove some no longer relevant bitrot in the test envi… Jul 12, 2019
.gitattributes Add .gitattributes file to force dos-lineendings.pc to match CRLF sty… May 4, 2012
.gitignore buildsys: add support for building a profiled executable Mar 1, 2013
.mailmap add mailmap Jul 11, 2019
AUTHORS update AUTHORS using `git shortlog -e` Jul 11, 2019 add mailmap Jul 11, 2019
COPYING bump copyrights to 2018 Dec 31, 2017 Add Kyua tests Sep 18, 2016 Add remaining Meson files to be included in dist tarballs May 25, 2020
Makefile.lite pkgconf 1.6.2. (closes #38, #40, #41) Jul 11, 2019
NEWS update NEWS May 31, 2020 update README [ci skip] Jul 12, 2019 initial libtoolization for libpkgconf Sep 6, 2015 pkgconf 1.7.3. May 31, 2020 build: install libpkgconf .pc file Dec 14, 2016 meson: remove some autotools cruft Jun 3, 2020
meson_options.txt meson: Add option to build without kyua for tests (#175) Mar 7, 2018
pkg.m4 Update pkg.m4 to latest upstream version (0.29.1) (#116) Mar 7, 2017

pkgconf status

pkgconf is a program which helps to configure compiler and linker flags for development libraries. It is similar to pkg-config from

libpkgconf is a library which provides access to most of pkgconf's functionality, to allow other tooling such as compilers and IDEs to discover and use libraries configured by pkgconf.

using pkgconf with autotools

Implementations of pkg-config, such as pkgconf, are typically used with the PKG_CHECK_MODULES autoconf macro. As far as we know, pkgconf is compatible with all known variations of this macro. pkgconf detects at runtime whether or not it was started as 'pkg-config', and if so, attempts to set program options such that its behaviour is similar.

In terms of the autoconf macro, it is possible to specify the PKG_CONFIG environment variable, so that you can test pkgconf without overwriting your pkg-config binary. Some other build systems may also respect the PKG_CONFIG environment variable.

To set the environment variable on the bourne shell and clones (i.e. bash), you can run:

$ export PKG_CONFIG=/usr/bin/pkgconf

comparison of pkgconf and pkg-config dependency resolvers

pkgconf builds an acyclic directed dependency graph. This allows for the user to more conservatively link their binaries -- which may be helpful in some environments, such as when prelink(1) is being used. As a result of building a directed dependency graph designed for the specific problem domain provided by the user, more accurate dependencies can be determined.

Current release versions of pkg-config, on the other hand, build a database of all known pkg-config files on the system before attempting to resolve dependencies, which is a considerably slower and less efficient design. Efforts have been made recently to improve this behaviour.

As of the 1.1 series, pkgconf also fully implements support for Provides rules, while pkg-config does not. pkg-config only provides the --print-provides functionality as a stub. There are other intentional implementation differences in pkgconf's dependency resolver verses pkg-config's dependency resolver in terms of completeness and correctness, such as, for example, how Conflicts rules are processed.

linker flags optimization

As previously mentioned, pkgconf makes optimizations to the linker flags in both the case of static and shared linking in order to avoid overlinking binaries and also simplifies the CFLAGS and LIBS output of the pkgconf tool for improved readability.

This functionality depends on the pkg-config module properly declaring it's dependency tree instead of using Libs and Cflags fields to directly link against other modules which have pkg-config metadata files installed.

Doing so is discouraged by the freedesktop tutorial anyway.

compatibility with pkg-config

We do not provide bug-level compatibility with pkg-config.

What that means is, if you feel that there is a legitimate regression versus pkg-config, do let us know, but also make sure that the .pc files are valid and follow the rules of the pkg-config tutorial, as most likely fixing them to follow the specified rules will solve the problem.

compiling pkgconf and libpkgconf on UNIX

pkgconf is basically compiled the same way any other autotools-based project is compiled:

$ ./configure
$ make
$ sudo make install

If you are installing pkgconf into a custom prefix, such as /opt/pkgconf, you will likely want to define the default system includedir and libdir for your toolchain. To do this, use the --with-system-includedir and --with-system-libdir configure flags like so:

$ ./configure \
     --prefix=/opt/pkgconf \
     --with-system-libdir=/lib:/usr/lib \
$ make
$ sudo make install

compiling pkgconf and libpkgconf with CMake (usually for Windows)

pkgconf is compiled using CMake on Windows. In theory, you could also use CMake to build on UNIX, but this is not recommended at this time as it pkgconf is typically built much earlier than CMake.

$ mkdir build
$ cd build
$ cmake ..
$ make
$ sudo make install

There are a few defines such as SYSTEM_LIBDIR, PKGCONFIGDIR and SYSTEM_INCLUDEDIR. However, on Windows, the default PKGCONFIGDIR value is usually overridden at runtime based on path relocation.

pkg-config symlink

If you want pkgconf to be used when you invoke pkg-config, you should install a symlink for this. We do not do this for you, as we believe it is better for vendors to make this determination themselves.

$ ln -sf pkgconf /usr/bin/pkg-config

release tarballs

Release tarballs are available at Please only use the tarballs from


You can report bugs at

There is a mailing list at

You can contact us via IRC at #pkgconf at

You can’t perform that action at this time.