| 15 Sep 2024 |
 svrana | K900: thx! would like to use libpipewire actually, but reading the docs wasn't sure how to get the list-objects output from it. | 19:20:39 |
| svrana | oh I was looking looking at the rust pipewire module. i'll look at libpipewire. | 19:22:03 |
| svrana | meh, pipewire example code does just that but was too thick to realize it. thx for steering me straight. | 19:40:40 |
| 16 Sep 2024 |
 @ryoschin:matrix.org | How should I use wasm-pack with the rust-overlay? Download it using cargo, systemPackages, or? | 18:11:26 |
| @ryoschin:matrix.org | * How should I use wasm-pack with the rust-overlay? Do I download it using cargo, systemPackages, or? | 18:11:32 |
| @ryoschin:matrix.org | Found my answer here: https://gist.github.com/oxalica/310d9a1ba69fd10123f2d70dc6e00f0b | 18:41:41 |
|  silentlurker joined the room. | 19:56:12 |
| 17 Sep 2024 |
|  Li-ion changed their profile picture. | 16:18:32 |
| Li-ion changed their display name from Ms. Connection to D. Tritus. | 16:19:41 |
|  @arexon:matrix.org changed their profile picture. | 16:57:52 |
| 18 Sep 2024 |
|  (artur 'manuel) changed their profile picture. | 23:00:30 |
| 19 Sep 2024 |
| @arexon:matrix.org left the room. | 09:20:05 |
 Gaétan Lepage | Do you bother fixing VERGEN warnings (complaining about not finding git and thus not being able to fill the VERGEN_* variables) ? | 11:50:46 |
 Alyssa Ross | lots of packages do — plenty of examples in Nixpkgs | 11:52:41 |
| Gaétan Lepage | Oh yes, I know about the cosmic ones for instance. I was wondering whether it was important or not.
I will go for it as it cannot hurt :) | 12:05:43 |
| Alyssa Ross | exactly | 12:11:57 |
| 20 Sep 2024 |
|  alice joined the room. | 03:37:14 |
 Theo Paris | Hmm should I make a new issue since this is closed? https://github.com/nix-community/home-manager/issues/3482#issuecomment-2362875487 | 05:48:46 |
| Theo Paris | * Hmm should I make a new issue in nixpkgs itself since this is closed? https://github.com/nix-community/home-manager/issues/3482#issuecomment-2362875487 | 05:49:00 |
| Theo Paris | I ran nix develop on a flake with rustc in nativeBuildInputs and then cargo run and it failed. I then added iconv to buildInputs on darwin and it worked | 05:49:42 |
| Alyssa Ross | That doesn't sound like an issue? | 07:28:26 |
| Alyssa Ross | Sometimes Rust programs depend on iconv, so you have to add an iconv input. | 07:28:45 |
 Enric Morales | What would be the process of overriding the attrs of a cross-compiling rustc (patches or whatever phase)? I am trying in different modifications but not quite hitting the correct incantation:
cross = import ../../../.. {
system = hostPlatform.system;
crossSystem = lib.systems.examples.arm-embedded // {
rust.rustcTarget = buildTarget.targetPlatform;
};
overlays = [
(final: prev: {
rustc = prev.wrapRustc (
prev.rustc.unwrapped.overrideAttrs (
{
patches ? [ ],
...
}:
{
patches = patches ++ [ ./fix-rustc-bootstrap.patch ];
}
)
);
})
];
};
of course, if I remove pkgCross and the platform, the rustc will be properly overridden, but the cross-one being untouched. I tried overlaying and setting pkgsBuildTarget instead, but then encountered the following error:
error: attribute 'targetPackages' missing
| 09:33:24 |
| Enric Morales | * What would be the process of overriding the attrs of a cross-compiling rustc (patches or whatever phase)? The derivation would be inside nixpkgs. I am trying in different modifications but not quite hitting the correct incantation:
cross = import ../../../.. {
system = hostPlatform.system;
crossSystem = lib.systems.examples.arm-embedded // {
rust.rustcTarget = buildTarget.targetPlatform;
};
overlays = [
(final: prev: {
rustc = prev.wrapRustc (
prev.rustc.unwrapped.overrideAttrs (
{
patches ? [ ],
...
}:
{
patches = patches ++ [ ./fix-rustc-bootstrap.patch ];
}
)
);
})
];
};
of course, if I remove pkgCross and the platform, the rustc will be properly overridden, but the cross-one being untouched. I tried overlaying and setting pkgsBuildTarget instead, but then encountered the following error:
error: attribute 'targetPackages' missing
| 09:34:08 |
| Alyssa Ross | We don't generally build a separate cross rustc | 09:37:02 |
| Alyssa Ross | Just a cross std | 09:37:05 |
| Alyssa Ross | (see fastCross in Nixpkgs)
| 09:37:12 |
| Enric Morales | In reply to @qyliss:fairydust.space
(see fastCross in Nixpkgs)
OK! I'll check fastCross then, thanks Alyssa Ross! | 10:08:51 |
| Enric Morales | having read that comment in rustc.nix and a bit more of the buildPhase, my patch would need to be applied to build the std: it applies to the configure script, as upstream has a [bug[(https://github.com/rust-lang/rust/issues/130602) that prevents setting, e.g. the linker options for targets which have a dot. It's what I tried to address last week by changing the configure method. | 10:22:58 |
| Enric Morales | * having read that comment in rustc.nix and a bit more of the buildPhase, my patch would need to be applied to build the std: it applies to the configure script, as upstream has a bug that prevents setting, e.g. the linker options for targets which have a dot. It's what I tried to address last week by changing the configure method. | 10:23:21 |
