crane/docs
Simon Žlender aa5dcd0518
Splice overrideToolchain (#652)
---------

Co-authored-by: Ivan Petkov <ivanppetkov@gmail.com>
2024-06-29 11:29:52 -07:00
..
advanced Try to avoid IFD in vendorCargoDeps and crateNameFromCargoToml; also avoid recommending nesting cleanCargoSource and path (#641) 2024-06-10 20:53:46 -07:00
examples Add workspace example (#597) 2024-04-21 22:23:03 +00:00
faq Splice overrideToolchain (#652) 2024-06-29 11:29:52 -07:00
introduction Try to avoid IFD in vendorCargoDeps and crateNameFromCargoToml; also avoid recommending nesting cleanCargoSource and path (#641) 2024-06-10 20:53:46 -07:00
.gitignore Add Crane book (#199) 2022-12-26 14:27:13 -08:00
API.md Splice overrideToolchain (#652) 2024-06-29 11:29:52 -07:00
book.toml book: add CNAME 2022-12-26 14:37:04 -08:00
CHANGELOG.md book: fix references 2022-12-26 14:55:25 -08:00
custom_cargo_commands.md Try to avoid IFD in vendorCargoDeps and crateNameFromCargoToml; also avoid recommending nesting cleanCargoSource and path (#641) 2024-06-10 20:53:46 -07:00
customizing_builds.md Try to avoid IFD in vendorCargoDeps and crateNameFromCargoToml; also avoid recommending nesting cleanCargoSource and path (#641) 2024-06-10 20:53:46 -07:00
getting-started.md Try to avoid IFD in vendorCargoDeps and crateNameFromCargoToml; also avoid recommending nesting cleanCargoSource and path (#641) 2024-06-10 20:53:46 -07:00
highlight.js Add Crane book (#199) 2022-12-26 14:27:13 -08:00
introduction.md Add Crane book (#199) 2022-12-26 14:27:13 -08:00
local_development.md Try to avoid IFD in vendorCargoDeps and crateNameFromCargoToml; also avoid recommending nesting cleanCargoSource and path (#641) 2024-06-10 20:53:46 -07:00
overriding_derivations.md Splice overrideToolchain (#652) 2024-06-29 11:29:52 -07:00
patching_dependency_sources.md vendorCargoDeps: allow arbitrary overrides when vendoring sources (#615) 2024-05-18 23:39:46 +00:00
README.md book: fix references 2022-12-26 14:55:25 -08:00
source-filtering.md Try to avoid IFD in vendorCargoDeps and crateNameFromCargoToml; also avoid recommending nesting cleanCargoSource and path (#641) 2024-06-10 20:53:46 -07:00
SUMMARY.md vendorCargoDeps: allow arbitrary overrides when vendoring sources (#615) 2024-05-18 23:39:46 +00:00

Crane

A Nix library for building cargo projects.

  • Source fetching: automatically done using a Cargo.lock file
  • Incremental: build your workspace dependencies just once, then quickly lint, build, and test changes to your project without slowing down
  • Composable: split builds and tests into granular steps. Gate CI without burdening downstream consumers building from source.

Features

  • Automatic vendoring of dependencies in a way that works with Nix
    • Alternative cargo registries are supported (with a minor configuration change)
    • Git dependencies are automatically supported without additional configuration.
      • Cargo retains the flexibility to only use these dependencies when they are actually needed, without forcing an override for the entire workspace.
  • Reusing dependency artifacts after only building them once
  • clippy checks
  • rustfmt checks
  • cargo-doc generation
  • And support for a number of popular tools such as:

Getting Started

The easiest way to get started is to initialize a flake from a template:

# Start with a comprehensive suite of tests
nix flake init -t github:ipetkov/crane#quick-start

Otherwise check out the examples and templates for more detailed examples. An API Reference is also available.

Compatibility Policy

Breaking changes can land on the master branch at any time, so it is recommended you use a versioning strategy when consuming this library (for example, using something like flakes or niv).

Tagged releases will be cut periodically and changes will be documented in the CHANGELOG. Release versions will follow Semantic Versioning.

The test suite is run against the latest stable nixpkgs release, as well as nixpkgs-unstable. Any breakage on those channels is considered a bug and should be reported as such.

License

This project is licensed under the MIT license.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion by you, shall be licensed as MIT, without any additional terms or conditions.