| 29 Mar 2026 |
 dish [Fox/It/She] | from looking at bootstrap i think they're still built so you have to remove them before running install | 20:24:18 |
 whispers [& it/fae] | nope, they aren't build until installPhase in my logs | 20:25:32 |
| dish [Fox/It/She] | huh interesting | 20:25:46 |
| whispers [& it/fae] | * | 20:25:55 |
| whispers [& it/fae] | i think because we specifically do ./x.py build library cargo; just ./x.py build does far more builds than we need | 20:26:43 |
| dish [Fox/It/She] | im looking and there doesn't appear to be any flags to disable running generate-copyright | 20:28:59 |
| dish [Fox/It/She] | probably since they don't expect this usecase | 20:30:25 |
| dish [Fox/It/She] | and per bootstrap.example.toml, installing the extended tools will always install the rust-installer tools, with no apparent way to disable that either | 20:30:57 |
| dish [Fox/It/She] | i might have missed something though since bootstrap's logic is pretty complex | 20:31:07 |
 emily | I'm much more concerned about mrustc's ability to keep up with both LLVM and Rust than about a few extra hours of bootstrap | 21:02:39 |
| whispers [& it/fae] | Redacted or Malformed Event | 21:05:06 |
| whispers [& it/fae] | Redacted or Malformed Event | 21:06:11 |
| whispers [& it/fae] | * | 21:06:22 |
| whispers [& it/fae] | * | 21:06:33 |
| whispers [& it/fae] | * | 21:07:23 |
| whispers [& it/fae] | * the fact that, had we been doing this before mrustc 0.12, this would've been 10 hours of building rust compilers on our laptop to get up to stable makes that effectively impossible, and mrustc is a one person project that has a very hard job so it's very likely to lag | 21:07:36 |
| 30 Mar 2026 |
 Charles | is there a way to tell buildRustPackage to only include one of the binaries in the output in a workspace with multiple binaries? | 01:58:00 |
| Charles | i could just rm in postInstall but like, they don't need to be built in the first place | 02:00:02 |
| Charles | okay, buildAndTestSubdir works | 02:02:15 |
 eveeifyeve | Charles: You could specify to build a specific package only. | 03:05:57 |
| Charles | i know about the --package option but it wasn't clear to me if there was an intended way to pass that to cargo while using buildRustPackage | 03:06:32 |
| eveeifyeve | * Charles: You could specify to build a specific package. | 03:06:34 |
| Charles | and also that message is pretty much free of information | 03:06:53 |
| eveeifyeve | It's intended way to parse it if you want to build a specific package. Note you must also do it for the test phase as well. | 03:07:36 |
| dish [Fox/It/She] | I believe buildAndTestSubdir is the intended way to build a single binary | 03:08:14 |
| Charles | so my question kinda implies that i know that cargo can do this on its own, in addition to explicitly asking how to do this in the context of buildRustPackage. how do you suggest i do what you are telling me to do, precisely, in terms of, say, some example nix code? | 03:09:18 |
| eveeifyeve | cargoBuildFlags = [ "--package <package>" ]; & cargoTestFlags = [ "--package <package>" ];? | 03:10:57 |
| eveeifyeve | But also the suggestion from dish [Fox/It/She] works as well. | 03:11:37 |
| Charles | okay, so maybe just lead with that next time instead of basically repeating my question back at me | 03:11:36 |
| Charles | should i elaborate/rephrase? | 03:14:26 |
