From 065da7698d7c51c093d061714df289ee6e81641c Mon Sep 17 00:00:00 2001 From: Harry Askham Date: Fri, 18 Oct 2024 10:26:51 +0100 Subject: [PATCH] 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. --- doc/stdenv/multiple-output.chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/stdenv/multiple-output.chapter.md b/doc/stdenv/multiple-output.chapter.md index 5e86d2aa3d56..09fdba01c44a 100644 --- a/doc/stdenv/multiple-output.chapter.md +++ b/doc/stdenv/multiple-output.chapter.md @@ -21,7 +21,7 @@ In the Nix language the individual outputs can be reached explicitly as attribut 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).) -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.) +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. ## Writing a split derivation {#sec-multiple-outputs-}