From 41e5db72f90b26317b983be1afc2ae39be6a4483 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 28 Apr 2025 04:11:57 +0000 Subject: pkg-config support; prepare for 2.4.1.0 Signed-off-by: Laurent Bercot --- INSTALL | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) (limited to 'INSTALL') diff --git a/INSTALL b/INSTALL index 0c63e81..555c2cc 100644 --- a/INSTALL +++ b/INSTALL @@ -27,6 +27,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 ------------- -- cgit v1.3.1