| 1 Oct 2022 |
 x10an14 | The default_features = false fixed it, many many thanks for all your help these last days. Now itis commit, push, and bedtime. | 02:20:58 |
|  cbrewster joined the room. | 19:28:35 |
| 3 Oct 2022 |
|  amesgen joined the room. | 23:21:40 |
| 4 Oct 2022 |
 Mic92 | John Ericson: Have you looked into building rust targets in our default rustc before? | 16:29:11 |
| Mic92 | I would be interested to build some sort ouf multi-output rustc derivation that also has webasm and musl. | 16:29:40 |
 Alyssa Ross | joerg: I've briefly thought about it, and it would be complicated due to the need to have the libcs available for other targets. | 17:48:55 |
| Alyssa Ross | I think it would be possible but not too easy. | 17:49:17 |
| Mic92 | qyliss: at least webasm doesn't need one. | 17:54:20 |
| Alyssa Ross | Yeah, that one would be easier. | 17:54:45 |
| Alyssa Ross | In that case, you should be able to override pkgsStatic.buildPackages.rustc to also include the webassembly target with the existing package, right? | 17:55:32 |
| Alyssa Ross | And then you'd have a compiler that could do glibc, musl, and webassembly. | 17:56:14 |
| Alyssa Ross | If there are any targets that we can turn on "for free" like webassembly, adding those by default would make sense I think | 17:57:13 |
| Alyssa Ross | That should just be a case of changing the default value of the package option, I think. | 17:58:00 |
| x10an14 | Could I somehow configure a flake to perform its compilation steps in a (multi-layered) docker image? I can't see support for this (AFAIU) in dockerTools.
Ideally I'd like my flake defined default package to be built in a docker container, then having resulting binary copied out for any final/distroless container image (the latter of which dockerTools can produce just fine.) | 18:05:54 |
 John Ericson | Mic92 Alyssa Ross is Rustc itself always multi-target? | 19:12:38 |
| John Ericson | I wish we could just build the standard library and rustc with crate2nix and separately | 19:12:53 |
| John Ericson | bypass rustbuild altogether | 19:13:03 |
| Alyssa Ross | Ericson2314: you give it a list of targets to support | 19:18:54 |
| John Ericson | Alyssa Ross: is that for building stadandard libraries or compiler features, though? | 19:23:08 |
| John Ericson | my guess is just standard libraries | 19:23:21 |
| Alyssa Ross | why would it be any different than clang? | 19:23:41 |
| Alyssa Ross | and like, it has to be multi-target or cross-compiling wouldn't work | 19:24:21 |
| Alyssa Ross | Because it's the same rustc that gets used for build and host. | 19:24:30 |
| John Ericson | well i mean I htink it is unlike LLVM where you can choose what backends to build as apart of libllvm | 19:24:54 |
| John Ericson | I don't think rustc has very much backend-specific code, except for maybe wasm, and I think most of it is uncondiitonal | 19:25:16 |
| Alyssa Ross | so why wouldn't it be multi-target? | 19:25:42 |
| Alyssa Ross | maybe I'm misunderstanding you | 19:25:46 |
| John Ericson | we're agreeing :) | 19:26:33 |
| Alyssa Ross | ah :) | 19:26:42 |
| John Ericson | I did some crate2nix bare metal cross things I need to upstream more for work | 19:27:48 |
