package compiler and linker metadata toolkit
C Shell M4 Groff Makefile
Latest commit f540ece Jan 20, 2017 @kaniini kaniini pkgconf 1.2.0.
Permalink
Failed to load latest commit information.
doc libpkgconf: client: add pkgconf_client_[get|set]_prefix_varname() Jan 20, 2017
libpkgconf add support for making paths relocatable (closes #103) Jan 20, 2017
scripts Add travis hacks to get kyua Sep 18, 2016
tests add support for making paths relocatable (closes #103) Jan 20, 2017
.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
.travis.yml Add travis hacks to get kyua Sep 18, 2016
AUTHORS Update AUTHORS based on git history. Jul 25, 2012
COPYING Update copyrights to 2017. Dec 28, 2016
Kyuafile.in Add Kyua tests Sep 18, 2016
Makefile.am add support for making paths relocatable (closes #103) Jan 20, 2017
NEWS update NEWS Jan 21, 2017
README.md update README wrt fd.o pkg-config commit c53385b5 Dec 25, 2016
autogen.sh initial libtoolization for libpkgconf Sep 6, 2015
configure.ac pkgconf 1.2.0. Jan 21, 2017
getopt_long.c configure: kill --enable-strict-mode, entirely pointless Nov 5, 2016
getopt_long.h getopt_long: fixups, remove dependency on libpkgconf etc. Sep 6, 2015
libpkgconf.pc.in build: install libpkgconf .pc file Dec 14, 2016
main.c main: add --dont-define-prefix for feature parity with pkg-config Jan 21, 2017
pkg.m4 Include PKG_CHECK_VAR macro for reading variables in .pc files Feb 24, 2013
pkgconf.1 pkgconf manpage: document --define-prefix, --dont-define-prefix, --pr… Jan 21, 2017

README.md

pkgconf Build Status Documentation Status

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

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 frameworks 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

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 \
     --with-system-includedir=/usr/include
$ make
$ sudo make install

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 /usr/bin/pkgconf /usr/bin/pkg-config

release tarballs

Release tarballs are available at https://distfiles.dereferenced.org/pkgconf/.

Please do not use the github tarballs as they are not pristine (instead generated by github everytime a download occurs).

reporting bugs

See https://github.com/pkgconf/pkgconf/issues.

Also you can contact us at #pkgconf at irc.freenode.net.