| 17 Aug 2022 |
|  greaka joined the room. | 20:23:57 |
| 18 Aug 2022 |
|  Florian | W3F changed their profile picture. | 09:20:05 |
| 19 Aug 2022 |
|  kayla (she/they) changed their display name from kayla.fire to kayla (she/they). | 01:39:48 |
|  Burrito (Marius) joined the room. | 15:04:15 |
| 21 Aug 2022 |
| greaka changed their display name from greaka ⚡️ to greaka . | 09:25:58 |
|  crushing-smite joined the room. | 10:55:08 |
| crushing-smite left the room. | 11:00:23 |
| 23 Aug 2022 |
|  Echo joined the room. | 00:50:14 |
|  Yureka (she/her) changed their display name from Yuka (she/her) to Yureka (she/her). | 10:42:51 |
| 24 Aug 2022 |
|  underpantsgnome changed their display name from tinybronca to underpantsgnome. | 23:01:37 |
| 25 Aug 2022 |
|  shanesveller joined the room. | 15:32:25 |
| 29 Aug 2022 |
|  aidalgol joined the room. | 20:58:40 |
| 30 Aug 2022 |
|  aru joined the room. | 14:43:04 |
| aru left the room. | 14:56:50 |
| 1 Sep 2022 |
|  typetetris joined the room. | 08:15:39 |
| typetetris | I have a project with several libs and apps in a single workspace. But I would like to package the apps separately. How do I prevent rebuilds in unrelated apps, if only the source of another app is touched?
Is splitting the repository/workspace the only pragmatic option?
The build system (naersk, cargo2nix, etc ...) would need to be aware of this and only include needed sources, but I am not aware of one doing that. | 08:19:04 |
 dpc | typetetris: You could possibly build the whole workspace, and then use another derivation to copy some binaries from that workspace build. | 18:34:35 |
| dpc | typetetris: Alternatively, crane can run cargo build --bin <cargo-bin> and create a binary out of it, which I use to build single-binary containers, like this: https://github.com/fedimint/fedimint/blob/6624d833de202417da1255759076f4c3f09ac3cf/flake.nix#L179 | 18:35:41 |
| dpc | I imagine cargo2nix and naersk might have similar functionality. | 18:36:11 |
| 2 Sep 2022 |
| typetetris | Hmm, would have to try this. But I would expect it to rebuild the single-binary build everytime unrelated sources in the same workspace change. Those build system don't usually filter sources on components to be build. | 05:32:41 |
| typetetris | Of course, that is a very specific requirement. | 05:32:56 |
| typetetris | So it is ok, they don't do this. | 05:33:08 |
|  problems changed their display name from ash (it/its) 🏳️⚧️ to problems. | 14:09:44 |
| 4 Sep 2022 |
|  dusk joined the room. | 16:01:21 |
| 5 Sep 2022 |
|  enemycube joined the room. | 14:33:01 |
 newam | I'm trying to build embedded rust firmware with nix, but not having much success with the recommendations in the rust-section of the nix manual, if anyone here has experience with this I could use some help 😃
https://discourse.nixos.org/t/building-embedded-rust-firmware-with-nix/21477
| 16:18:39 |
 Xe Iaso | how do i make a rust compiler with the wasm32-wasi target enabled? | 16:56:27 |
 a-kenji | I used the oxalica overlay here: https://github.com/zellij-org/zellij/blob/main/.nix/plugins.nix | 16:57:49 |
| a-kenji | This is where the toolchain is specified: https://github.com/zellij-org/zellij/blob/main/rust-toolchain.toml, but i am not quite sure how to do it without an overlay. | 16:59:00 |
| Xe Iaso | :+1: thanks | 17:04:55 |
