| 4 Aug 2025 |
 dramforever | i'm surprised it even got this far | 18:10:02 |
 emily | the cool thing about splicing is how it doesn't work at all with like foo.package = foo.override { … }; | 18:10:05 |
| emily | like it only actually helps the boring easy case | 18:10:17 |
| dramforever | yeah i think the entirety of overrides.nix needs a callPackage-ification or like pkgsXY-ification | 18:10:50 |
| dramforever | In reply to @emilazy:matrix.org
I think it's not because the main package set isn't spliced and nobody knows why i think the funniest part is iirc pkgs in _module.args in nixos is spliced | 18:16:57 |
| emily | well… | 18:17:16 |
| emily | https://github.com/NixOS/nixpkgs/pull/416276 | 18:17:24 |
| emily | I spent several days being like wtf is cross NixOS just totally busted until I discovered this bug | 18:17:32 |
| emily | but yes by default it is | 18:17:47 |
 kjeremy | this didn't seem to change anything | 18:40:31 |
| emily | your whole splicing is messed up | 18:45:33 |
| emily | can you do this as not an overlay | 18:45:40 |
| kjeremy | I'm not sure. It's even worse than this in reality. This is an unholy abomination. We're a few years out of date with nixpkgs and the latest nix-ros-overlay so I'm trying to jam these packages into our older nix-ros-overlay with an overlay and then use rust from nix-unstable to compile the zenoh packages since they require a newer toolchain. Miraculously it works natively but dies horribly during cross | 18:48:11 |
| emily | uhhh | 18:49:01 |
| kjeremy | yep | 18:49:09 |
| emily | you should be happy it can build anything :D | 18:50:05 |
| kjeremy | honestly it's pretty impressive that nix can do this when non-cross | 18:50:30 |
| emily | anyway any time you nativeBuildInputs you must explicitly use buildPacakges | 18:50:45 |
| emily | since no splicing | 18:50:51 |
| kjeremy | Okay! So I got it to use the right packages by using buildPackages.{rustPlatform, cargo, rustc}. It turns out I had to tell zeno to pass the right architecture down to cmake with cmakeFlags = [ "-DZENOHC_CUSTOM_TARGET=aarch64-unknown-linux-gnu" ]; | 20:06:51 |
|  kfiz joined the room. | 20:33:12 |
| kfiz changed their display name from kfiz 🏳️⚧️ to kfiz. | 21:18:59 |
|  impqxr joined the room. | 21:52:01 |
| 5 Aug 2025 |
|  isabel changed their profile picture. | 09:49:06 |
| kfiz set a profile picture. | 20:14:27 |
| 6 Aug 2025 |
|  vidariondr set a profile picture. | 18:30:52 |
| 7 Aug 2025 |
|  The Little Waltz joined the room. | 17:31:33 |
 damccull | How do I find out what "buildRustPackage" has as far as options? Like, I see it has a 'buildFeatures' option by looking at someone else's code, but does it have a buildPackages option, for instance? Where would I look to find that out?
Basically I want to specify which particular binary in the cargo.toml to build. Normally would do this with cargo build --package mybin but not sure how in the buildRustPackage helper.
| 23:10:42 |
| damccull | * How do I find out what "buildRustPackage" has as far as options? Like, I see it has a 'buildFeatures' option by looking at someone else's code, but does it have a cargoPackages option, for instance? Where would I look to find that out?
Basically I want to specify which particular binary in the cargo.toml to build. Normally would do this with cargo build --package mybin but not sure how in the buildRustPackage helper.
| 23:12:04 |
| dramforever | In reply to @damccull:matrix.org
How do I find out what "buildRustPackage" has as far as options? Like, I see it has a 'buildFeatures' option by looking at someone else's code, but does it have a cargoPackages option, for instance? Where would I look to find that out?
Basically I want to specify which particular binary in the cargo.toml to build. Normally would do this with cargo build --package mybin but not sure how in the buildRustPackage helper.
maybe buildAndTestSubdir? it's a bit confusingly documented i agree | 23:18:36 |
