c4patino/nixpkgs
1
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2026-07-06 17:13:24 -05:00
Code Issues Projects Releases Packages Wiki Activity

doc/stdenv: add a note about strictDeps

Browse source
This commit is contained in:
Tobias Mayer 2024-11-10 09:19:49 +01:00 • committed by Gutyina Gergő
commit cda3c8a1d5
No known key found for this signature in database
2 changed files with 11 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

3
doc/redirects.json
View file

@ -788,6 +788,9 @@
"var-stdenv-depsTargetTargetPropagated": [
"index.html#var-stdenv-depsTargetTargetPropagated"
],
"var-stdenv-strictDeps": [
"index.html#var-stdenv-strictDeps"
],
"ssec-stdenv-attributes": [
"index.html#ssec-stdenv-attributes"
],

8
doc/stdenv/stdenv.chapter.md
View file

@ -487,6 +487,14 @@ The propagated equivalent of `buildInputs`. This would be called `depsHostTarget
The propagated equivalent of `depsTargetTarget`. This is prefixed for the same reason of alerting potential users.
##### `strictDeps` {#var-stdenv-strictDeps}
When using native compilation, `stdenv` is lenient towards incorrect placement of a dependency into one of the dependency lists described above. That means a dependency needed at runtime often works, even if it is only present in `nativeBuildInputs`. Vice-versa, dependencies containing binaries that need to be executed during the build will work even if they are only listed in `buildInputs`.
While convenient for getting to a package quickly, this behavior can break cross-compilation. Adding `strictDeps = true` as a parameter to `mkDerivation` or any of its language specific wrappers disables this behavior.
The specialized `build*` functions for dlang, emacs, go, nim, ocaml, python, and rust enable this option by default.
## Attributes {#ssec-stdenv-attributes}
### Variables affecting `stdenv` initialisation {#variables-affecting-stdenv-initialisation}