zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix formatting in packaging guide (#33714)

Browse Source
This commit is contained in:
iarspider
2022-11-05 03:00:16 +01:00
committed by GitHub
parent d7cb790f88
commit 9becc82dfc
1 changed files with 3 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
lib/spack/docs/packaging_guide.rst
View File

@@ -4406,16 +4406,9 @@ In addition to invoking the right compiler, the compiler wrappers add
flags to the compile line so that dependencies can be easily found. flags to the compile line so that dependencies can be easily found.
These flags are added for each dependency, if they exist: These flags are added for each dependency, if they exist:
Compile-time library search paths * Compile-time library search paths: ``-L$dep_prefix/lib``, ``-L$dep_prefix/lib64``
* ``-L$dep_prefix/lib`` * Runtime library search paths (RPATHs): ``$rpath_flag$dep_prefix/lib``, ``$rpath_flag$dep_prefix/lib64``
* ``-L$dep_prefix/lib64`` * Include search paths: ``-I$dep_prefix/include``
Runtime library search paths (RPATHs)
* ``$rpath_flag$dep_prefix/lib``
* ``$rpath_flag$dep_prefix/lib64``
Include search paths
* ``-I$dep_prefix/include``
An example of this would be the ``libdwarf`` build, which has one An example of this would be the ``libdwarf`` build, which has one
dependency: ``libelf``. Every call to ``cc`` in the ``libdwarf`` dependency: ``libelf``. Every call to ``cc`` in the ``libdwarf``