crate2nix
crate2nix copied to clipboard
rebuild only changed crates in CI with crate2nix and nix
### Current Behavior When specifying a `withTest = true` via `override` on a generate crate from `crate2nix`, the compilation does not work because the doesn't find the dependencies specified in...
See - https://github.com/rust-lang/wg-cargo-std-aware - https://doc.rust-lang.org/cargo/reference/unstable.html#build-std - https://internals.rust-lang.org/t/dogfooding-z-build-std-in-rustbuild/13775/13 I am very interested using this for nice incremental builds, native and cross, building each crate of the standard library and also rustc...
Hello, Random thought coming to my mind: right now, crate2nix doesn't (AFAIK) allow building the examples, meaning that it's not possible to just use nix to build&run examples. What do...
I'm hoping to compile [`libzmq-sys`](https://github.com/jean-airoldie/libzmq-rs) using crate2nix but ran into an issue. `libzmq-sys` uses cmake and [vendored sources](https://github.com/jean-airoldie/zeromq-src-rs) to compile and statically link zmq. I tried the following override: ```nix...
I was able to use crate2nix on this project. I think I just did a `cargo update`. crate2nix 0.8.0 rustc 1.45.0-nightly (a08c47310 2020-05-07) ``` ❯ nix-build trace: root_crate is deprecated...
For example, try generating and building https://github.com/aahancoc/tree_magic/tarball/0.2.3 The binary fails to build since it can't find `clap`. Here's the relevant Cargo.toml snippet: ```toml [features] cli = ["clap", "tabwriter", "scoped_threadpool", "walkdir",...
If you use `crate2nix` with your own project, you can either use a `tools.nix` based workflow in which `Cargo.nix` is generated in a derivation and imported. Or you can pregenerate...
https://github.com/kolloch/crate2nix/issues/76 introduced `tools.nix` and nix functions for generating the build files in derivations. That allows users to skip checking in the generated `Cargo.nix`. This does not work for "sub modules"...
AFAIK Running doctests typically involves invoking `rustdoc --test` with the rest of the flags being pretty much the same as when building a plain rustc crate.
Currently, `crate2nix` can't use build profiles specified in `Cargo.toml`. It would be great if it was able to and had an option to select which one to use.