Robotnix | 228 Members | |
| Build Android (AOSP) using Nix | https://github.com/nix-community/robotnix | 68 Servers |
| Sender | Message | Time |
|---|---|---|
| 1 Dec 2025 | ||
| * Doesn't robotnix support aarch64-linux?! I have just ran
| 16:21:33 | |
Download screenshot-2025-12-01_19:20:40.png | 16:22:04 | |
| I think i asked this question and the answer i think i got was "no because android ships rebuilt binaries but only for x86" | 16:39:56 | |
| This fact may have changed but you'd need to research that | 16:51:48 | |
| (I did remember right, yay!) | 16:58:37 | |
| what about the first question haha | 17:52:08 | |
| What is exactly the purpose of using the pre-build binaries by google in android-nixpkgs? As they don't provide any for aarch64. | 20:54:28 | |
| 2 Dec 2025 | ||
| I might be new here but it seems that most if not all pkgs in android-nixpkgs are now available under nixpkgs androidenv.* This might be new idk is there something am missing? I am now changing android-nixpkgs to androidenv.* as it support aarch64, Please notify me if there is something I am missing. Thanks! | 01:49:21 | |
| * I might be new here but it seems that most if not all pkgs in android-nixpkgs are now available under nixpkgs androidenv.* This might be new idk is there something am missing? I am now changing android-nixpkgs to androidenv.* (not sure if it support aarch64), Please notify me if there is something I am missing. Thanks! | 01:56:49 | |
okay so I just took a look at it, and it seems like that's gonna be a bit more difficult. github:TrebleDroid/treble_manifest works by taking the LineageOS git-repo manifest as a base, and <remove-project ... />ing a bunch of the upstream LineageOS directories. Back when I wrote repo2nix I decided against supporting these git-repo directives because they'd have required me to wade through the messy Python source code of git-repo (and yes, it already was difficult figuring out the override behaviour for the default/project-specific remotes) | 13:10:39 | |
i suppose it'd be manageable to approximate the upstream git-repo behaviour for <remove-project> directives just enough for that specific manifest to work, but imo that'd be misguided because then it'd probably start misbehaving in other cases using <remove-project> | 13:12:13 | |
| it's an inherent drawback of the "rewrite git-repo in rust" approach I took, in contrast to danielrf's original approach of patching git-repo :/ | 13:12:45 | |
| 3 Dec 2025 | ||
| * Following this tutorial: It seems that i just need to add https://github.com/TrebleDroid/treble_manifest/tree/android-15.0 to | 06:06:43 | |
| * Following this tutorial: It seems that i just need to add https://github.com/TrebleDroid/treble_manifest/tree/android-15.0 to | 06:06:59 | |
for the other cases just warn about that repo2nix couldn't handle this! | 06:08:21 | |
* for the other cases just warn that repo2nix couldn't handle this! | 06:08:35 | |
| Why exacly does the manifast download go? Should just the host system install go?!
| 06:10:01 | |
| * Why exacly does the manifast download go? Shouldn't just the host system install go?!
| 06:10:42 | |
| As I got an error because it didn't ship an aarch64 go prebuilt binary! | 06:13:05 | |
| Or I might just remove them manually haha | 06:16:38 | |
| Why does blueprint being used while it got archived four years ago? https://github.com/google/blueprint | 19:04:44 | |
How exactly could I use/run modules/repo2nix.nix? (I am little bit nix noob)I didn't see anywhere in the project for an usage! | 20:13:20 | |
| 4 Dec 2025 | ||
| 01:44:44 | ||
| 04:20:29 | ||
| I think that I have enough ram. I get about a third of the way through the build before it fails with
| 06:49:30 | |
| My config is
| 06:50:10 | |
| Ah, hmm; that usually means this file was generated while keeping the nix store permissions of the source files | 06:53:19 | |
| I just bought a used pixel 9 pro so I'm going to try building for caiman | 06:54:01 | |
| We have patches that make the builsystem chmod such instances but it's whack-a-mole | 06:54:16 | |
| You'd have to figure out which part of the build puts this file in this place and how | 06:55:00 | |