| 11 Feb 2025 |
 Andy Hamon | crate2nix lets you override the impl of buildRustCrate. So I made an impl with transforms arguments on the way in and tacks on extraRustcOpts = ["--target aarch64-apple-ios"]; | 04:42:27 |
| Andy Hamon | (and I already have a custom rustPlatform from rust-overlay which has additional targets added) | 04:44:47 |
| Andy Hamon | not toooo worried about a lack of correctness here from a cross compiling point of view since I only want to build a staticlib | 04:47:56 |
| Andy Hamon | not sure yet if it works with dependencies or not, crate has 0 deps. But I don't see why it wouldn't | 04:48:48 |
| Andy Hamon | also no idea if my .a file even works | 04:48:57 |
| Andy Hamon | anyways, I wish crate2nix had better hooks for overriding aspects of the build en-mass. I already had to do something similar to add custom filtering to src. I just discovered a very long comment to myself explaining why its not as simple as it seems since we also want to propagate through invocations of override | 05:06:30 |
|  Dirk Van Haerenborgh changed their display name from Dirk Van Haerenborgh @ FOSDEM to Dirk Van Haerenborgh. | 13:03:24 |
 rosssmyth | Hello. How am I supposed to use makeRustPlatform? I have code like this:
msrv_toolchain = pkgs.pkgsBuildHost.rust-bin.fromRustupToolchainFile ./rust-toolchain.toml;
rustPlatform = pkgs.makeRustPlatform {
cargo = msrv_toolchain;
rustc = msrv_toolchain;
};
...
mypackage = pkgs.callPackage mkThing { inherit rustPlatform };
and I am getting an error that says
error: attribute 'buildPackage' missing
at /nix/store/njnqqp2qgx2jfzk8jbfxghhm8x3gb4vl-source/flake.nix:37:7:
36| in
37| rustPlatform.buildPackage {
The package is just something like
mkThing = {
pkgs,
rustPlatform,
...
}:
rustPlatform.buildPackage {
...
}
| 15:38:38 |
| rosssmyth | * Hello. How am I supposed to use makeRustPlatform? I have code like this:
msrv_toolchain = pkgs.pkgsBuildHost.rust-bin.fromRustupToolchainFile ./rust-toolchain.toml;
rustPlatform = pkgs.makeRustPlatform {
cargo = msrv_toolchain;
rustc = msrv_toolchain;
};
...
mypackage = pkgs.callPackage mkThing { inherit rustPlatform };
and I am getting an error that says
error: attribute 'buildPackage' missing
at /nix/store/njnqqp2qgx2jfzk8jbfxghhm8x3gb4vl-source/flake.nix:37:7:
36| in
37| rustPlatform.buildPackage {
The package is just something like
{
pkgs,
rustPlatform,
...
}:
rustPlatform.buildPackage {
...
}
| 15:38:59 |
| rosssmyth | And I can't use the debugger cause it just segfaults upon hitting any breakpoints 🥲 | 15:40:45 |
| rosssmyth | Stupid mistake #2 this week. Ignore the above. 🥲 | 19:00:52 |
| 12 Feb 2025 |
|  maounomusume joined the room. | 00:02:06 |
 Gaétan Lepage | Hey, I was not able to find how to specify build features when using Maturin.
I tried buildFeatures but it didn't propagate into maturin's flags. | 08:58:02 |
| Gaétan Lepage | Seems like the best way is maturinBuildFlags. | 09:45:14 |
|  Kira changed their display name from kira to Kira. | 19:59:40 |
 cleverca22 | when using rustPlatform.buildRustPackage, is there a way to set the version in nix automatically from the cargo lock file? | 20:36:07 |
 @marcel:envs.net | Do you mean something like that?
https://github.com/dd-ix/sflow_exporter/blob/main/package.nix#L8 | 20:36:39 |
| cleverca22 | ah, that looks good, let me try it | 20:37:06 |
| cleverca22 | In reply to @marcel:envs.net
Do you mean something like that?
https://github.com/dd-ix/sflow_exporter/blob/main/package.nix#L8 yep, that works perfectly! | 20:38:21 |
| cleverca22 | now to do the same thing on nodejs, thats far simpler, but also basically identical to the above! | 20:46:50 |
| cleverca22 | manifest = pkgs.lib.importJSON ./package.json; and done! | 20:48:54 |
| 13 Feb 2025 |
 Sandro 🐧 | Niklas Korz Alyssa Ross do you have any idea how I can myself bring the mitmproxy update forward? My rust compiler building skills are not enough to implement what you suggested above... | 14:28:37 |
 Alyssa Ross | The issue still hasn't really been properly reported upstream | 14:31:36 |
| Alyssa Ross | Only in a comment | 14:31:38 |
| Alyssa Ross | So I think the next step would be to properly report the issue upstream | 14:31:54 |
| Alyssa Ross | but ultimately rustc's build system needs to be fixed by someone
| 14:32:06 |
| Alyssa Ross | there's not even anything in the compiler that needs to be fixed, just its build system | 14:32:36 |
 Niklas Korz | In reply to @qyliss:fairydust.space
there's not even anything in the compiler that needs to be fixed, just its build system Yeah I still haven't quite understood what needs to be fixed unfortunately | 14:35:59 |
| Niklas Korz | I digged through the docs part of the build chain and that seemed to have handling for no std targets already | 14:36:21 |
| Niklas Korz | * I digged through the docs part of the build chain and that seemed to have handling for no_std targets already | 14:36:38 |
