Maximilian Bosch 6b23cfe689 rustPlatform: add buildAndTestSubdir-argument ... There are several tarballs (such as the `rust-lang/rust`-source) with a `Cargo.toml` at root and several sub-packages (with their own Cargo.toml) without using workspaces[1]. In such a case it's needed to move into a subdir to only build the specified sub-package (e.g. `rustfmt` or `rsl`), however the artifacts are at `/target` in the root-dir of the build environment. This breaks the build since `buildRustPackage` searches for executables in `target` (which is at the build-env's root) at the end of the `buildPhase`. With the optional `buildAndTestSubdir`-argument, the builder moves into the specified subdir using `pushd`/`popd` during `buildPhase` and `checkPhase`. Also moved the logic to find executables and libs to the end of the `buildPhase` from a custom `postBuild`-hook to fix packages with custom `build`/`install`-procedures such as `uutils-coreutils`. [1] https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html		2020-05-13 01:47:17 +02:00
..
default.nix	rust-analyzer: 2020-04-06 -> 2020-04-20	2020-04-23 17:11:04 +08:00
generic.nix	rustPlatform: add buildAndTestSubdir-argument	2020-05-13 01:47:17 +02:00
update.sh	vscode-extensions.rust-analyzer: use global NPM packages to share dependencies	2020-04-11 16:01:12 +08:00
wrapper.nix