From c1a440b6cc781696ac23373f2b71e895cfc2c517 Mon Sep 17 00:00:00 2001 From: Arthur Gautier Date: Tue, 19 Oct 2021 05:37:05 +0000 Subject: [PATCH] doc: rust: target escape hatch has been removed As far as I can tell, a8efb2053fd9c1e2fea97699754b5071e94c1649 removed the `target =` escape hatch. See #112804 This commit removes it from the documentation. Signed-off-by: Arthur Gautier --- doc/languages-frameworks/rust.section.md | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/doc/languages-frameworks/rust.section.md b/doc/languages-frameworks/rust.section.md index b2f045b11b3..26eb9e26bd0 100644 --- a/doc/languages-frameworks/rust.section.md +++ b/doc/languages-frameworks/rust.section.md @@ -237,22 +237,6 @@ where they are known to differ. But there are ways to customize the argument: --target /nix/store/asdfasdfsadf-thumb-crazy.json # contains {"foo":"","bar":""} ``` -Finally, as an ad-hoc escape hatch, a computed target (string or JSON file -path) can be passed directly to `buildRustPackage`: - -```nix -pkgs.rustPlatform.buildRustPackage { - /* ... */ - target = "x86_64-fortanix-unknown-sgx"; -} -``` - -This is useful to avoid rebuilding Rust tools, since they are actually target -agnostic and don't need to be rebuilt. But in the future, we should always -build the Rust tools and standard library crates separately so there is no -reason not to take the `stdenv.hostPlatform.rustc`-modifying approach, and the -ad-hoc escape hatch to `buildRustPackage` can be removed. - Note that currently custom targets aren't compiled with `std`, so `cargo test` will fail. This can be ignored by adding `doCheck = false;` to your derivation.