Skip to content

Commit 065da76

Browse files
harryaskhambjornfor
authored andcommitted
doc: Cross-link mention of symlinkJoin in 'Multiple-output packages'
Per #36886, would have saved me some time today to have the trivial builder more visible.
1 parent c4a6d1b commit 065da76

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/stdenv/multiple-output.chapter.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In the Nix language the individual outputs can be reached explicitly as attribut
2121

2222
When a multiple-output derivation gets into a build input of another derivation, the `dev` output is added if it exists, otherwise the first output is added. In addition to that, `propagatedBuildOutputs` of that package which by default contain `$outputBin` and `$outputLib` are also added. (See [](#multiple-output-file-type-groups).)
2323

24-
In some cases it may be desirable to combine different outputs under a single store path. A function `symlinkJoin` can be used to do this. (Note that it may negate some closure size benefits of using a multiple-output package.)
24+
In some cases it may be desirable to combine different outputs under a single store path. The `symlinkJoin` builder can be used to do this. (See [](#trivial-builder-symlinkJoin)). Note that this may negate some closure size benefits of using a multiple-output package.
2525

2626
## Writing a split derivation {#sec-multiple-outputs-}
2727

0 commit comments

Comments
 (0)