RGBCube/Site
1
Fork 0
mirror of https://github.com/RGBCube/Site synced 2025-07-30 20:47:46 +00:00
Code Issues Activity Actions

dump(build-systems.no-gnulib): update

Browse source
This commit is contained in:
RGBCube 2025-07-19 23:57:59 +03:00
parent a6cab132b2
commit e1c05dc85a
Signed by: RGBCube
SSH key fingerprint: SHA256:CzqbPcfwt+GxFYNnFVCqoN5Itn4YFrshg1TrnACpA5M
1 changed files with 85 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

91
site/dump/build-systems/no-gnulib.md
View file

@ -103,12 +103,12 @@ look, it's all 140 lines of code!
## But it can be even better
Nixpkgs has `pkgs.buildRustCrate`, to build crates without Cargo, but currently
doesn't use it for most packages, so it doesn't have crate-level incremental
rebuilds. This may change in the future, and when it does, compiling Rust
programs will take a fraction of the time because you aren't building
dependencies over and over and over and over again, and can utilize
`cache.nixos.org`, or any other cache.
Nixpkgs has [`pkgs.buildRustCrate`](https://noogle.dev/f/pkgs/buildRustCrate),
to build crates without Cargo, but currently doesn't use it for most packages,
so it doesn't have crate-level incremental rebuilds. This may change in the
future, and when it does, compiling Rust programs will take a fraction of the
time because you aren't building dependencies over and over and over and over
again, and can utilize `cache.nixos.org`, or any other cache.
It will also decrease the amount of lines you'll have to write in Nixpkgs
package specifications, because you'll no longer have to specify all external
@ -118,6 +118,85 @@ dependencies will be configured in a
so a top-level Rust program that uses a crate that requires `liburing` won't
actually see `liburing` when being compiled.
<blockquote>
You can actaully use this right now with
[`cargo2nix`](https://github.com/cargo2nix/cargo2nix) or
[`crate2nix`](https://github.com/nix-community/crate2nix), though expect some
headaches. (I recently spent a few hours getting `crate2nix` to work on a huge
codebase with a lot of native dependencies, and `aws-lc-sys` was the biggest
headache on darwin)
<details>
<summary>The extra crate overrides I ended up with, if it helps.</summary>
```nix
{ pkgs, ... }:
{
openssl = old: {
buildInputs = old.buildInputs or [ ] ++ [
pkgs.openssl
];
};
openssl-sys = old: {
RUSTFLAGS = "--cfg ossl111 --cfg ossl110 --cfg ossl101";
"${pkgs.stdenv.buildPlatform.rust.cargoEnvVarTarget}_OPENSSL_DIR" = "${pkgs.openssl.dev}";
OPENSSL_NO_VENDOR = "1";
OPENSSL_STATIC = "0";
};
aws-lc-sys = old: {
nativeBuildInputs = old.nativeBuildInputs or [ ] ++ [
pkgs.cmake
pkgs.go
pkgs.libclang
pkgs.perl
pkgs.nasm
];
env.CFLAGS = "-D_DARWIN_C_SOURCE"; # Hours of my life wasted to figure this out.
};
librocksdb-sys = old: {
buildInputs = old.buildInputs or [ ] ++ [
pkgs.zlib
pkgs.zstd
pkgs.bzip2
pkgs.lz4
];
};
tokio = old: {
extraRustcOpts = old.extraRustcOpts or [ ] ++ [
"--cfg tokio_unstable"
];
};
uvm_syn = old: {
extraRustcOpts = old.extraRustcOpts or [ ] ++ [
"-Awarnings"
];
};
pyo3_build_config = old: {
buildInputs = old.buildInputs or [ ] ++ [
pkgs.python313
];
};
}
```
I also had to patch the `Cargo.nix` generator because it was not handling or
even exposing a way to enable extra cfg flags separately, but maybe this is
fixed in `cargo2nix`?
Anyway, we do not talk about the general state of Nix/Nixpkgs/NixOS tooling.
(But it's still better than every other distro out there)
</details>
</blockquote>
## Takeaway...?
**Package management and build systems aren't hard, your tools are just bad.**