nix: don't drag rust toolchain into system closures
This commit is contained in:
parent
7800c19280
commit
bff8e24e56
3 changed files with 9 additions and 42 deletions
8
PLAN.md
8
PLAN.md
|
|
@ -955,11 +955,9 @@ No `tokio`, no `zbus`, no `dbus-*`.
|
|||
|
||||
`flake.nix` ships:
|
||||
|
||||
- A **devshell** with rust toolchain (via `rust-overlay` for pinned
|
||||
channel; default to a stable release pinned in
|
||||
`rust-toolchain.toml`), `pkg-config`, `pipewire`'s dev outputs,
|
||||
`clang` (for bindgen if invoked by deps), `socat` (handy for poking
|
||||
the IPC), `jq`.
|
||||
- A **devshell** with the Rust toolchain from nixpkgs, `pkg-config`,
|
||||
`pipewire`'s dev outputs, `clang` (for bindgen if invoked by deps),
|
||||
`socat` (handy for poking the IPC), `jq`.
|
||||
- A **package** output (`packages.<system>.default`) that builds the
|
||||
daemon + CLI with `rustPlatform.buildRustPackage`. v0 uses
|
||||
`cargoLock.lockFile`. Crane can come later if incremental builds in
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue