doc/stdenv: improve autoPatchelfHook description
* Add id * Mention rpath * The control variables do not really have to be env vars (though without structuredAttrs there is not a difference)
This commit is contained in:
parent
67325b12c6
commit
55e7f95265
@ -2001,7 +2001,7 @@ addEnvHooks "$hostOffset" myBashFunction
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry xml:id="setup-hook-autopatchelfhook">
|
||||||
<term>
|
<term>
|
||||||
autoPatchelfHook
|
autoPatchelfHook
|
||||||
</term>
|
</term>
|
||||||
@ -2010,15 +2010,13 @@ addEnvHooks "$hostOffset" myBashFunction
|
|||||||
This is a special setup hook which helps in packaging proprietary software in that it automatically tries to find missing shared library dependencies of ELF files based on the given <varname>buildInputs</varname> and <varname>nativeBuildInputs</varname>.
|
This is a special setup hook which helps in packaging proprietary software in that it automatically tries to find missing shared library dependencies of ELF files based on the given <varname>buildInputs</varname> and <varname>nativeBuildInputs</varname>.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
You can also specify a <envar>runtimeDependencies</envar> environment variable which lists dependencies that are unconditionally added to all executables.
|
You can also specify a <varname>runtimeDependencies</varname> variable which lists dependencies to be unconditionally added to <glossterm>rpath</glossterm> of all executables.
|
||||||
</para>
|
|
||||||
<para>
|
|
||||||
This is useful for programs that use <citerefentry>
|
This is useful for programs that use <citerefentry>
|
||||||
<refentrytitle>dlopen</refentrytitle>
|
<refentrytitle>dlopen</refentrytitle>
|
||||||
<manvolnum>3</manvolnum> </citerefentry> to load libraries at runtime.
|
<manvolnum>3</manvolnum> </citerefentry> to load libraries at runtime.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
In certain situations you may want to run the main command (<command>autoPatchelf</command>) of the setup hook on a file or a set of directories instead of unconditionally patching all outputs. This can be done by setting the <envar>dontAutoPatchelf</envar> environment variable to a non-empty value.
|
In certain situations you may want to run the main command (<command>autoPatchelf</command>) of the setup hook on a file or a set of directories instead of unconditionally patching all outputs. This can be done by setting the <varname>dontAutoPatchelf</varname> environment variable to a non-empty value.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
The <command>autoPatchelf</command> command also recognizes a <parameter class="command">--no-recurse</parameter> command line flag, which prevents it from recursing into subdirectories.
|
The <command>autoPatchelf</command> command also recognizes a <parameter class="command">--no-recurse</parameter> command line flag, which prevents it from recursing into subdirectories.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user