Nix Rust | 673 Members | |
| Rust | 153 Servers |
| Sender | Message | Time |
|---|---|---|
| 3 Nov 2025 | ||
in general though, how would I do that for something that hasn't been packaged already? Do I have to fully package it myself, or is there a way to just plug in the name on crates.io and maybe a rust toolchain derivation or something and have it be built and installed as if by cargo install? | 17:04:42 | |
| Packaging it yourself. https://github.com/nix-community/nix-init can help for simpler cases But things like adding required native libraries or patching weird build.rs things would need manual fixes after. | 17:10:30 | |
Figured it out! Needed to add llvmPackages.bintools. | 17:40:48 | |
and this: RUSTFLAGS -C link-self-contained=-linker | 17:41:25 | |
| 4 Nov 2025 | ||
| 08:22:50 | ||
| 20:06:43 | ||
| 20:06:49 | ||
| 6 Nov 2025 | ||
| 08:32:46 | ||
| 7 Nov 2025 | ||
| 11:40:00 | ||
| 18:30:19 | ||
| 18:41:58 | ||
| 22:41:10 | ||
| 9 Nov 2025 | ||
| 15:03:52 | ||
| 15:23:51 | ||
| 11 Nov 2025 | ||
| 09:22:30 | ||
| 19:20:27 | ||
| Hi all -- relative novice, hoping someone can help me run a rust binary built outside of nix in a nixosTest (as part of a bisect to fix a problem upstream). I've been using runCommand to copy it into the test image with Including all the buildInputs for an xorg-based linux system from https://github.com/espanso/espanso/blob/dev/nix/espanso.nix Anyone know why copying a binary that runs fine outside nix into a NixOS VM would give me this wx-related missing symbol error when all the required libraries seem to be linked (at least I don't see anything obviously missing based on | 20:41:54 | |
| Do you need to do something special during runtime to trigger it ? | 21:29:43 | |
To trigger the error? No, even a --version triggers it. | 21:37:40 | |
| Can't reproduce, seems to work on both my machine and nixosTest. Unless you use headless test for some reason. | 21:41:10 | |
| No, not headless. You are building espanso from source on a non-nixos system with standard Rust tooling, copying the binary while patching with autoPatchelfHook, and then running it in nix, and it's working? | 21:42:48 | |
| No, downloading .deb from releases page, doing all that and it runs. Let me clean up things and push. | 21:52:28 | |
| Oh interesting. My ultimate goal is a git bisect on the source to fix an upstream bug that was introduced sometime in the last year and a half (ugh), so I'll need to be able to build from source, but that's a reasonable way to test. I'll give that a shot. | 21:54:02 | |
| 21:55:41 | |
I do not think binary in their release .deb should be that different from build result from other distro. | 21:57:20 | |
| Actually if binary built on other distro is the one with problems, maybe it is just a mismatch of wxGTK32 versions. | 22:09:52 | |
| Hopefully not, I renovated the build system prior to the 2.3 release using a pretty standard ubuntu build process. Building now. | 22:10:00 | |
| That could totally be it. | 22:10:12 | |
| I bet you're right. Yup the deb version is working fine. But now I'm not sure how to get a matching wxGTK32 version on Arch, but I can look into that. It certainly would be much easier to just bisect by setting Are you aware of any way that I can override | 22:14:27 | |
| Looks like wxgtk 3.2.8.1 on nix, 3.2.8.1-2 on arch. | 22:15:52 | |