diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2025-04-28 08:09:45 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska@appnovation.com> | 2025-04-28 08:09:45 +0000 |
| commit | f0370bb20e7aeac1e80054459a8ba9e7021fa59d (patch) | |
| tree | 7bd860c0a819dfe7ac43a276b7aceeea16dfdef7 /INSTALL | |
| parent | 54540f5c71444be103d72f436378043170d4e735 (diff) | |
| download | pamela-f0370bb20e7aeac1e80054459a8ba9e7021fa59d.tar.gz | |
Move to new system
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL | 31 |
1 files changed, 29 insertions, 2 deletions
@@ -10,8 +10,8 @@ Build Instructions - Linux-PAM version 1.3.0 or later: http://www.linux-pam.org/library/ This software will run on any operating system that implements -POSIX.1-2008, available at: - http://pubs.opengroup.org/onlinepubs/9699919799/ +POSIX.1-2024, available at: + http://pubs.opengroup.org/onlinepubs/9799919799/ as well as Linux-PAM. As of September 2024, this means only Linux. @@ -42,6 +42,33 @@ this, the pamelad binary (which expects Linux-PAM, not pamela, in security/pam_appl.h) may not be built correctly. +* 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 ------------- |