| 3 Dec 2025 |
 rosssmyth | For an example of the caching, you can see what I did with Wild. Basically the assumption is "the Cargo.lock and flake.lock files do not change very often (compared to the rest of the souce)"
So there's a dedicated job that refreshes the cache when the lockfiles change
Then another job for running with the cached dependencies
And a cron job to periodically update the flake lockfile
| 22:37:03 |
| rosssmyth | You can use nightly and beta with buildRustPackage just as easily as the other options, so I wouldn't really say that's an advantage. It's even shown in the reference how to | 22:38:21 |
| rosssmyth | You just can't in Nixpkgs | 22:38:34 |
 neobrain | rosssmyth: How do you handle day-to-day development? Do you enter a nix shell or do you always nix run/build? If it's purely the former, I'm guessing the main benefit of the caching is for CI? | 22:39:26 |
| neobrain | * rosssmyth: How do you handle day-to-day development? Do you enter a nix shell (and then use Cargo manually) or do you always nix run/build? If it's purely the former, I'm guessing the main benefit of the caching is for CI? | 22:39:45 |
| rosssmyth | The packages that allow it are rust-overlay and the other one I can't remember
https://nixos.org/manual/nixpkgs/unstable/#using-rust-nightly-in-a-derivation-with-buildrustpackage | 22:40:03 |
| rosssmyth | Generally both. The caching in CI is pretty much always a win, then caching when I'm just doing day-to-day dev is also great cause I always like to verify that things build alright in the sandbox when I'm developing | 22:41:26 |
 Marien Zwart | In reply to @rosssmyth:matrix.org
The packages that allow it are rust-overlay and the other one I can't remember
https://nixos.org/manual/nixpkgs/unstable/#using-rust-nightly-in-a-derivation-with-buildrustpackage https://github.com/nix-community/fenix ? | 22:42:22 |
| rosssmyth | yeah | 22:42:30 |
| neobrain | I see, makes sense. Thanks for the explanation! | 22:43:29 |
| 4 Dec 2025 |
|  Ido Samuelson joined the room. | 01:45:35 |
|  onur-ozkan joined the room. | 04:20:40 |
|  @curid:matrix.org left the room. | 08:59:20 |
|  isabel changed their profile picture. | 16:42:04 |
|  Tanja (she/her) changed their display name from Tanja (she/her) to Tanja (she/her) - ☎️ 4201. | 18:09:36 |
| 5 Dec 2025 |
|  👉@crystallinefire:chat.solarpunk.moe changed their display name from EVA-01 to 👉@crystallinefire:chat.solarpunk.moe. | 17:17:01 |
| 7 Dec 2025 |
|  magnetophon joined the room. | 13:39:01 |
| 8 Dec 2025 |
 Ralith | some part of the toolchain seems to have started stripping the RUNPATH from proc macro crates that link shared libraries in the environment. Anyone have a fix? | 05:16:32 |
| Ralith | it's set to /path/to/my/project/outputs/out/lib, which is pretty weird because that doesn't even exist... | 05:17:46 |
| Ralith | dpc (migrated to @dpc:dpc.pw): looks like you reported something similar at https://discourse.nixos.org/t/rust-binaries-losing-runpath-on-one-machine-only-fedora/34324, did you ever sort it out? | 05:19:23 |
| rosssmyth | Could you provide code? | 16:09:23 |
| rosssmyth | It's hard to know what going on with just a description | 16:09:36 |
|  @hythera:matrix.org joined the room. | 21:31:24 |
| 9 Dec 2025 |
| Ralith | in my environment it reproduces easily with cargo test in https://github.com/Ralith/vk-shader-macros/. Build should have a rust toolchain and SHADERC_LIB_DIR = "${pkgs.shaderc.lib}/lib"; in the environment. | 00:23:17 |
| Ralith | you'll get the same error (plus some downstream noise), and you can see:
~/src/vk-shader-macros> readelf -d target/debug/deps/libvk_shader_macros-5228c9752deafce6.so
Dynamic section at offset 0xda180 contains 31 entries:
Tag Type Name/Value
0x000000000000001d (RUNPATH) Library runpath: [/home/ralith/src/vk-shader-macros/outputs/out/lib]
0x0000000000000001 (NEEDED) Shared library: [libshaderc_shared.so.1]
modulo variation in the filename, ofc
| 00:27:19 |
| rosssmyth | I meant the Nix code. | 03:17:25 |
| rosssmyth | I would like to use your exact setup | 03:17:34 |
| rosssmyth | So just saying "run cargo test" isn't that useful | 03:17:50 |
| rosssmyth | What does the environment look like, where did you get cargo, does this replicate in the sandbox | 03:18:12 |
| Ralith | the nix code is utterly trivial, it's a shell with rustChannels.stable.rust and the env var I mentioned | 04:04:38 |
