crate2nix
crate2nix copied to clipboard
rebuild only changed crates in CI with crate2nix and nix
Cargo has a questionable behaviour where ``` cargo build -pfoo cargo build -pbar ``` does not give the same result as ``` cargo build -pfoo -pbar ``` In the first...
Without this, if we do `nix run .#some-workspace-member`, it tries to run `$out/bin/rust_some-workspace-member` as it defaults to the package name. It'd be cool if `nix run .#flake` just worked.
not sure if this should be filed here or against nixpkgs, since it looks like the actual building is there, but it'd be nice if crates got a `.doc` output...
I can't figure out how to use `separateDebugInfo`. I guess I would need something like: ```nix { extraRustcOpts = ["-g"]; separateDebugInfo = true; } ``` and I think I would...
[*ring*](https://github.com/briansmith/ring) fails to build on i686-linux, because the target attributes are different compared to builds run with cargo directly. With cargo, the target_arch is `x86`, while with crate2nix it's `i686`.
I tried to use crate2nix along the "Choosing a Rust Version" readme part. My sample code had only one dependency, copypasta (version = "0.7"). Running nix-build returns the following error:...
e.g. when I have a `-sys` crate which links against C stuff using `build.rs`, and could reuse already installed stuff, it would be cool if I could declare a dependency...
In version `0.1.25` [mimalloc_rust](https://github.com/purpleprotocol/mimalloc_rust) switched from [cmake build to cc](https://github.com/purpleprotocol/mimalloc_rust/pull/58) which caused `multiple definition` errors to start showing up when linker is invoked on dylib, before that change everything worked...
e.g. currently I use something like this: https://github.com/zseri/crulz-rs/blob/4d6bb6367923e0018ff39e3471fd7c2c5c0c2b2e/flake.nix, but this boilerplate could be further reduced, I suppose. ```nix let progname = "crulz"; applist = [progname]; overlay = final: prev: {...
This project looks very useful, however there appear to be some incompatibilities with cargo. In particular, `libpulse-binding` fails to build. If there is a way to fix this ad-hoc, it...