| 29 Aug 2025 |
|  magic_rb changed their profile picture. | 19:30:58 |
| 2 Sep 2025 |
|  haras-unicorn joined the room. | 15:50:41 |
| 4 Sep 2025 |
 jaen | Wait, is this suddenly not dead anymore? And here I thought it's impossible to get it to build until I write an incremental AOSP build system xS Not sure if I should be happy or annoyed at not being smart enough xD | 20:23:51 |
 pentane ⭔ | the build system is still very much non-incremental | 20:24:26 |
| pentane ⭔ | all I did was bring stuff up to date | 20:24:38 |
| jaen | Yeah, I figured, the thing is I marvel at you being able to do that when Android builds for hours and a failure throws all the progress out the windows ;' ) | 20:25:17 |
| jaen | * Yeah, I figured, the thing is I marvel at you being able to do that when Android builds for hours and a failure throws all the progress out the window ;' ) | 20:25:32 |
 atemu12 | And wrote whole git-repo and room-service re-implementation in rust on the side.. ;) | 20:25:40 |
| atemu12 | * And wrote whole git-repo and room-service reimplementation in rust on the side.. ;) | 20:25:54 |
| atemu12 | * And wrote whole git-repo and roomservice re-implementation in rust on the side.. ;) | 20:26:01 |
| pentane ⭔ | it's actually quite possible if you liberally sprinkle printf debug statements into the build tooling via patches | 20:26:02 |
| atemu12 | The android build process itself isn't really the hard part (or wasn't) | 20:26:43 |
| atemu12 | As long as you get all the required sources and binaries into the env, it just works | 20:27:02 |
| atemu12 | I mean, that's how it works on googlers' workstations | 20:27:22 |
| jaen | I mean, it is certainly not impossible (as evidenced by you doing this), it's just that after n-th time of flushing hours of build time down the drain I gave up xD | 20:27:36 |
| jaen | Hence, the not being smart enough part xD | 20:27:44 |
| atemu12 | (okay, we do need to patch some things but they're quite generic) | 20:27:45 |
| jaen | * Hence, the "not being smart enough" part xD | 20:28:01 |
| pentane ⭔ | I think it's not you not being smart enough but just me being more masochistic than it's healthy for me lol | 20:28:22 |
| pentane ⭔ | Yeah, most of the issues I had to fix come from the downstream distributions (Lineage and Graphene), because they tend to make unreasonable assumptions re the build environment | 20:28:52 |
| pentane ⭔ | e.g.: currently trying to work around whatever the fuck this is https://github.com/GrapheneOS/adevtool/pull/225/files | 20:29:16 |
| atemu12 | Or rather unreasonable assumptions about how one acquires the sources | 20:29:28 |
| atemu12 | "Run this python script that queries all repos in the LineageOS org and fetch the repos that end in the device name" kind of shit | 20:30:06 |
| atemu12 | * "Run this python script that queries all repos in the LineageOS org and fetches the repos that end in the device name" kind of shit | 20:30:27 |
| pentane ⭔ | Yeah anyway | 20:30:56 |
| pentane ⭔ | Hopefully I'll get the graphene build to work this evening and tested tomorrow | 20:31:19 |
| jaen | Nice, I guess I can always continue writing my build tool for the lulz instead of just for getting my phone ROM to work xD | 20:32:38 |
| atemu12 | Build tool for what? | 20:33:08 |
| jaen | For AOSP. Basically there's this WIP thing - https://github.com/pdtpartners/nix-ninja - that lets you get nix-based incremental builds for projects using ninja with dynamic derivations. AOSP generates ninja files, but they are so humongous the Rust ninja implementation they use just chokes one them. I was trying to write one that doesn't choke to be able to finally update GrapheneOS in robotnix without going insane from time wasted on build failures. And since GrapheneOS is now up to date in robotnix, that particular reason is no longer there ¯\_(ツ)_/¯ | 20:55:13 |
| jaen | Anyway, I was probably going about it the wrong way, given that somebody has done it without that xD | 20:55:43 |
