aboutsummaryrefslogtreecommitdiffstats
path: root/INSTALL
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2025-04-27 19:00:05 +0000
committerLaurent Bercot <ska@appnovation.com>2025-04-27 19:00:05 +0000
commit7f6dabcd0c10f8dd0ab7828722543fa23478dba5 (patch)
treeeff5c940a0b2a21aaaba1e45d8785085c2627338 /INSTALL
parent74076f00bb2676a7b1f579595edff6c9b05728ab (diff)
downloads6-rc-7f6dabcd0c10f8dd0ab7828722543fa23478dba5.tar.gz
Prepare for 0.5.6.0, add pkg-config support, etc.
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL29
1 files changed, 28 insertions, 1 deletions
diff --git a/INSTALL b/INSTALL
index 8d46050..6b45d10 100644
--- a/INSTALL
+++ b/INSTALL
@@ -8,7 +8,7 @@ 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 version 2.13.2.0 or later: https://skarnet.org/software/s6/
This software will run on any operating system that implements
POSIX.1-2008, available at:
@@ -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
-------------