crane icon indicating copy to clipboard operation
crane copied to clipboard

A Nix library for building cargo projects. Never build twice thanks to incremental artifact caching.

Results 64 crane issues
Sort by recently updated
recently updated
newest added

We started complex builds with cross-compiled projects (think: Android app built for different targets, or multi-arch (`lipo`) MacOS binaries, or wasm + a native web server), it seemed like it...

From the [original report](https://github.com/ipetkov/crane/issues/417#issuecomment-1763450988) > Sorta unrelated and not really a crane issue imo, but I did notice that with `dontStrip = true` binaries tend to leave behind references to...

We've been using `buildDepsOnly` with `--workspace` to cache all the dependencies in the workspace. Unfortunately, this doesn't actually work properly if [feature unification](https://doc.rust-lang.org/cargo/reference/features.html#feature-unification) takes place. At least, I think that's...

Hi! Recently crane changed to symlinking rlib and rmeta files when reading dependencies. For the random reader, Crane generates the dependencies in one nix build, and then uses them in...

I'm looking for a way to build npm packages from compiled wasm binaries. For example, using `wasm-pack` (but right now I have problems with that see rustwasm/wasm-pack#1318). I've made a...

## Motivation Avoid copying big cargo build artifacts from the nix store, when using `cargoArtifacts`. This works by just symlinking everything in `target/release/build` and `target/release/deps`. and uses rsync to copy...

When I execute `cargo llvm-cov` directly, results seem to be fine. When I execute it in a Nix derivation using `crane.cargoLlvmCov`, it seems like it takes all dependencies into account...

needs reproduction

Right now `cargoExtraArgs = "--bin bin-target-name"` (usually[^1]) doesn't work if you only specify `lib.buildPackage` (i.e., you don't split out the two `lib.buildDepsOnly` and `lib.buildPackage` steps yourself). I think this is...

I’m not sure if this is a good idea, but if not I’d like to hear what the best alternative is (explicit separate `buildPackage` for each lib in the workspace?)...

Allows running cargo benchmarks easily via crane. ## Motivation Noticed this was missing in a project I'm working on [using crane](https://github.com/tweag/nickel/pull/1119/files#diff-206b9ce276ab5971a2489d75eb1b12999d4bf3843b7988cbe8d687cfde61dea0R220). Creating as a draft to gauge interest before sinking...