From d078dced9183e80786d8b3624fb0b9c3c459b55a Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Tue, 18 Apr 2023 17:56:03 +0200 Subject: INSTALL.md: packaging builds now use pkg-config --- INSTALL.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/INSTALL.md b/INSTALL.md index 2f3fd92d..9b042a2d 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -98,14 +98,16 @@ to an appropriate location in `PATH`. The main task is to ensure all the dependencies are available at sufficiently compatible versions. The full list of dependencies can be found in `etc/repos.json`. This file also specifies, in -the `"local_path"` attribute of `"local_bootstrap"`, the location -relative to `LOCALBASE` (typically `/usr` or `/usr/local`) that -is taken as root for the logical repository of that dependency. -If your distribution prefers to install each package in a separate -directory, you can always take `/` as `LOCALBASE` and adapt these -paths accordingly. The instructions on how to link those dependencies -are stored in the targets files in `etc/import.prebuilt`. Depending -on the packaging, the linking flags might need adaption as well. +the `"local_path"` attribute of `"pkg_bootstrap"`, the location +relative to `LOCALBASE` (typically `/usr` or `/usr/local`) that is +taken as root for the logical repository of that dependency. As, +however, library dependencies are taken via `pkg-config`, in most +cases, setting this attribute should not be necessary. The target +files for the dependencies can be found in `etc/import.pkgconfig`. +Possibly different names to be used by `pkg-config` can be adapted +there. If the environment variable `PKG_CONFIG_PATH` is set, the +bootstrap script forwards it to the build so that `pkg-config` can +pick up the correct files. The build command is the same (with the same positional arguments), however with the environment variable `PACKAGE` being present -- cgit v1.2.3