From cc62341cf526dfb3c925bcab5f022dfa9da2c24e Mon Sep 17 00:00:00 2001 From: Christopher Dilks Date: Thu, 14 Dec 2023 19:48:29 -0500 Subject: [PATCH] doc: update dependency_resolution.md --- doc/dependency_resolution.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/doc/dependency_resolution.md b/doc/dependency_resolution.md index 04e0110e..764dec60 100644 --- a/doc/dependency_resolution.md +++ b/doc/dependency_resolution.md @@ -10,16 +10,17 @@ Assuming a dependency is installed in `$prefix`, it uses one or more of the foll Take a look at each dependency's installation prefix to see which of these options are available. -One way of using these dependencies is with environment variables: +To use these dependencies with your software, they must be findable by its build system; +for `iguana`, the build system is `meson`, which accepts the build options ```bash -export PKG_CONFIG_PATH=$prefix/lib/pkgconfig -export CMAKE_PREFIX_PATH=$prefix +-Dpkg_config_path=$prefix/lib/pkgconfig +-Dcmake_prefix_path=$prefix ``` -Multiple paths are delimited by colons. +(where multiple paths are delimited by commas). -A better way is to use build options; for `meson`, use the following: +Environment variables may be used instead of build options for a general approach: ```bash --Dpkg_config_path=$prefix/lib/pkgconfig --Dcmake_prefix_path=$prefix +export PKG_CONFIG_PATH=$prefix/lib/pkgconfig +export CMAKE_PREFIX_PATH=$prefix ``` -Multiple paths are delimited by commas. +(where multiple paths are delimited by colons).