Pkg-config

pkg-config is a computer program that defines and supports a unified interface for querying installed libraries for the purpose of compiling software that depends on them. It allows programmers and installation scripts to work without explicit knowledge of detailed library path information. pkg-config was originally designed for Linux, but it is now also available for BSD, Microsoft Windows, macOS, and Solaris.

It outputs various information about installed libraries. This information may include:
 * Parameters (flags) for C or C++ compiler
 * Parameters (flags) for linker
 * Version of the package in question

The first implementation was written in shell. Later, it was rewritten in C using the GLib library.

Synopsis
When a library is installed (automatically through the use of an RPM, deb, or other binary packaging system or by compiling from the source), a  file should be included and placed into a directory with other   files (the exact directory is dependent upon the system and outlined in the pkg-config man page). This file has several entries.

These entries typically contain a list of dependent libraries that programs using the package also need to compile. Entries also typically include the location of header files, version information and a description.

Here is an example  file for libpng: This file demonstrates how  informs that its libraries can be found in   and its headers in , that the library name is  , and that the version is 1.2.8. It also gives the additional linker flags that are needed to compile code that uses this library.

Here is an example of usage of pkg-config while compiling:

pkg-config can be used by build automation software such as CMake.

Alternative implementations

 * pkgconf – Implementation of pkg-config without depending on GLib


 * u-config – Minimal implementation with first-class Windows support
 * PkgConfig – Pure-Perl Core-Only replacement for pkg-config
 * ruby-gnome/pkg-config – Implementation of pkg-config in Ruby