forked from mirrors/nixpkgs
6b23cfe689
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
27 lines
880 B
Nix
27 lines
880 B
Nix
{ stdenv, rustPlatform, Security }:
|
|
|
|
rustPlatform.buildRustPackage rec {
|
|
pname = "rustfmt";
|
|
inherit (rustPlatform.rust.rustc) version src;
|
|
|
|
# the rust source tarball already has all the dependencies vendored, no need to fetch them again
|
|
cargoVendorDir = "vendor";
|
|
buildAndTestSubdir = "src/tools/rustfmt";
|
|
|
|
# changes hash of vendor directory otherwise
|
|
dontUpdateAutotoolsGnuConfigScripts = true;
|
|
|
|
buildInputs = stdenv.lib.optional stdenv.isDarwin Security;
|
|
|
|
# As of 1.0.0 and rustc 1.30 rustfmt requires a nightly compiler
|
|
RUSTC_BOOTSTRAP = 1;
|
|
|
|
meta = with stdenv.lib; {
|
|
description = "A tool for formatting Rust code according to style guidelines";
|
|
homepage = "https://github.com/rust-lang-nursery/rustfmt";
|
|
license = with licenses; [ mit asl20 ];
|
|
maintainers = with maintainers; [ globin basvandijk ];
|
|
platforms = platforms.all;
|
|
};
|
|
}
|