WARNING

This is my experimental cargo branch which generates files in /tmp/nix during normal cargo build execution when using CARGO_NIX_BUILDER=fast.

In theory later one can then do:

nix build --file /tmp/nix/ -L

For now it is just an experiment.

Alternative calls:

CARGO_NIX_BUILDER=fast cargo build
CARGO_NIX_BUILDER=sandbox cargo build
CARGO_NIX_BUILDER= cargo build

cargo -Znix --config build.nix=\"fast\" build
cargo -Znix --config build.nix=\"sandbox\" build

todo

• -L needs to be reintegrated with propagatedBuildInputs concept so that

   rphtml v0.5.10 (/home/nixos/rphtml)
   ├── htmlentity v1.3.2
   │   ├── anyhow v1.0.97
   │   ├── lazy_static v1.5.0
   │   └── thiserror v1.0.69
   │       └── thiserror-impl v1.0.69 (proc-macro)
   │           ├── proc-macro2 v1.0.94
   │           │   └── unicode-ident v1.0.18
   │           ├── quote v1.0.39
   │           │   └── proc-macro2 v1.0.94 (*)
   │           └── syn v2.0.99
   │               ├── proc-macro2 v1.0.94 (*)
   │               ├── quote v1.0.39 (*)
   │               └── unicode-ident v1.0.18
   ├── lazy_static v1.5.0
   └── thiserror v1.0.69 (*)
  

  https://gist.github.com/qknight/cec3d2be284ab704ae88ee2da5726821

flake

{
  description = "The cargo-nix using example project flake";
  inputs = {
    nixpkgs.url      = "github:NixOS/nixpkgs/nixos-25.05";
    rust-overlay.url = "github:oxalica/rust-overlay";
  };
  outputs =
  { self, nixpkgs, flake-utils, rust-overlay }:
    flake-utils.lib.eachDefaultSystem
      (system:
        let
          overlays = [ (import rust-overlay) ];
          pkgs = import nixpkgs {
            inherit system overlays;
          };
          allPackages = import /tmp/nix/default.nix { inherit pkgs; };
        in
        with pkgs;
        rec {
          packages = allPackages // {
            inherit defaultPackage;
          };
          devShells.default = mkShell {
            buildInputs = [
              rust-bin.stable."1.86.0".default
            ];
          };
        }
      );
}

nix build .#anyhow-1_0_97 -L --impure --print-out-paths
nix build .#rphtml-0_5_10 -L --impure --print-out-paths

Cargo

Cargo downloads your Rust project’s dependencies and compiles your project.

To start using Cargo, learn more at The Cargo Book.

To start developing Cargo itself, read the Cargo Contributor Guide.

The Cargo binary distributed through with Rust is maintained by the Cargo team for use by the wider ecosystem. For all other uses of this crate (as a binary or library) this is maintained by the Cargo team, primarily for use by Cargo and not intended for external use (except as a transitive dependency). This crate may make major changes to its APIs.

Code Status

Code documentation: https://doc.rust-lang.org/nightly/nightly-rustc/cargo/

Compiling from Source

Requirements

Cargo requires the following tools and packages to build:

• cargo and rustc
• A C compiler for your platform
• git (to clone this repository)

Other requirements:

The following are optional based on your platform and needs.

• pkg-config — This is used to help locate system packages, such as libssl headers/libraries. This may not be required in all cases, such as using vendored OpenSSL, or on Windows.

• OpenSSL — Only needed on Unix-like systems and only if the vendored-openssl Cargo feature is not used.

  This requires the development headers, which can be obtained from the libssl-dev package on Ubuntu or openssl-devel with apk or yum or the openssl package from Homebrew on macOS.

  If using the vendored-openssl Cargo feature, then a static copy of OpenSSL will be built from source instead of using the system OpenSSL. This may require additional tools such as perl and make.

  On macOS, common installation directories from Homebrew, MacPorts, or pkgsrc will be checked. Otherwise it will fall back to pkg-config.

  On Windows, the system-provided Schannel will be used instead.

  LibreSSL is also supported.

Optional system libraries:

The build will automatically use vendored versions of the following libraries. However, if they are provided by the system and can be found with pkg-config, then the system libraries will be used instead:

• libcurl — Used for network transfers.
• libgit2 — Used for fetching git dependencies.
• libssh2 — Used for SSH access to git repositories.
• libz (aka zlib) — Used for data compression.

It is recommended to use the vendored versions as they are the versions that are tested to work with Cargo.

Compiling

First, you'll want to check out this repository

git clone https://github.com/rust-lang/cargo.git
cd cargo

With cargo already installed, you can simply run:

cargo build --release

Adding new subcommands to Cargo

Cargo is designed to be extensible with new subcommands without having to modify Cargo itself. See the Wiki page for more details and a list of known community-developed subcommands.

Releases

Cargo releases coincide with Rust releases. High level release notes are available as part of Rust's release notes. Detailed release notes are available in the changelog.

Reporting issues

Found a bug? We'd love to know about it!

Please report all issues on the GitHub issue tracker.

Contributing

See the Cargo Contributor Guide for a complete introduction to contributing to Cargo.

License

Cargo is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.

Third party software

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://www.openssl.org/).

In binary form, this product includes software that is licensed under the terms of the GNU General Public License, version 2, with a linking exception, which can be obtained from the upstream repository.

See LICENSE-THIRD-PARTY for details.