diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2025-04-27 11:27:08 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska@appnovation.com> | 2025-04-27 11:27:08 +0000 |
| commit | ba7a3d22cb728a4230bb78dba3b6b46907dcefee (patch) | |
| tree | 1edda83a6cef51e2f34fe8d3fbb96de92a5cc999 /INSTALL | |
| parent | 79e226cbaf64b20e85df75d2225a98bc2b3fe3dd (diff) | |
| download | utmps-ba7a3d22cb728a4230bb78dba3b6b46907dcefee.tar.gz | |
pkg-config support, prepare for 0.1.3.0, etc.
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL | 29 |
1 files changed, 28 insertions, 1 deletions
@@ -7,7 +7,7 @@ Build Instructions - A POSIX-compliant C development environment - GNU make version 3.81 or later - skalibs version 2.14.4.0 or later: https://skarnet.org/software/skalibs/ - - s6 version 2.13.1.1 or later: https://skarnet.org/software/s6/ + - s6 version 2.13.2.0 or later: https://skarnet.org/software/s6/ (this is only a run-time requirement, not a build-time one) This software will run on any operating system that implements @@ -29,6 +29,33 @@ POSIX.1-2008, available at: off them. +* pkg-config + ---------- + + pkg-config is a tool used by some Linux and BSD distributions, providing +a registry to store policy information about libraries exported by a +software package; that is supposed to make it easier to build software +depending on these libraries, by having a tool to automatically extract +the various flags to pass to the compiler and linker in order to correctly +build against these libraries. + This package supports pkg-config, but you need to explicitly ask for it: + - To use the pkg-config tool to *read* information from the registry and +use it to build *this* package: --with-pkgconfig[=PROG]. This assumes +PROG supports the pkg-config interface (as the popular pkgconf +implementation does). If PROG is not supplied, the PKG_CONFIG environment +variable is used to find the program to use, and if empty/unset, it defaults +to pkg-config. + - To build a .pc file for each library exported by this package, and then +install it to the pkg-config registry, in other words to *write* information +so that other software can use pkg-config to build against this package, +use --enable-pkgconfig. + + pkg-config and slashpackage (see below) configure options can be set +together, but the slashpackage convention provides its own installation +policies that generally make it unnecessary to use pkg-config. You +probably should not mix both. + + * Customization ------------- |