From f3a814c550c19cac46963cabade0d348999abe85 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 28 Apr 2025 08:40:16 +0000 Subject: Move to new system, support pkg-config Signed-off-by: Laurent Bercot --- INSTALL | 33 ++++++++++++++++++++++++++++++--- 1 file changed, 30 insertions(+), 3 deletions(-) (limited to 'INSTALL') diff --git a/INSTALL b/INSTALL index 91e05f6..ed65035 100644 --- a/INSTALL +++ b/INSTALL @@ -8,9 +8,9 @@ Build Instructions - GNU make version 3.81 or later - skalibs version 2.14.4.0 or later: https://skarnet.org/software/skalibs/ - execline version 2.9.7.0 or later: https://skarnet.org/software/execline/ - - s6 version 2.13.1.1 or later: https://skarnet.org/software/s6/ - - s6-rc version 0.5.5.1 or later: https://skarnet.org/software/s6-rc/ - - s6-linux-init version 1.1.2.2 or later: https://skarnet.org/software/s6-linux-init/ + - s6 version 2.13.2.0 or later: https://skarnet.org/software/s6/ + - s6-rc version 0.5.6.0 or later: https://skarnet.org/software/s6-rc/ + - s6-linux-init version 1.1.3.0 or later: https://skarnet.org/software/s6-linux-init/ * Standard usage @@ -26,6 +26,33 @@ Build Instructions 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 ------------- -- cgit v1.3.1