Robotnix | 244 Members | |
| Build Android (AOSP) using Nix | https://github.com/danielfullmer/robotnix | 75 Servers |
| Sender | Message | Time |
|---|---|---|
| 3 Jun 2024 | ||
| And then provide them to source.dirs | 23:13:07 | |
| Ok, I'll search around, thank you | 23:30:25 | |
| It does seem like they've migrated completely off of gitlab for lineage 21 btw | 23:30:44 | |
| No repos have lineage-21 branches | 23:30:55 | |
| 4 Jun 2024 | ||
| Got this from the lineageos chat room: https://luk1337.github.io/muppets/ | 00:03:41 | |
| And was told that I should only need what's there. | 00:04:48 | |
| This is what it responds with:
| 00:05:24 | |
| 11:13:47 | ||
Ok, I just successfully built lineageos locally with a standard build environment. I can confirm that the source device dir contains pantah, pantah-kernel, gs101, gs201, and gs-common with no corresponding vendor dir and builds successfully. | 22:48:18 | |
| Does this indicate that the robotnix code needs to change to not expect vendor dirs for those devices? | 22:48:33 | |
| I'm going to try adding a "noVendor" filter to device-dirs.json and filter those out in lineageos/default.nix | 23:59:54 | |
| 5 Jun 2024 | ||
Was able to successfully get the Robotnix source dir structure to match the structure in the standard build, but still getting the no kernel error Neither INSTALLED_KERNEL_TARGET nor INSTALLED_BOOTIMAGE_TARGET is defined when PRODUCT_OTA_ENFORCE_VINTF_KERNEL_REQUIREMENTS is true | 00:43:25 | |
Realizing that maybe the original choosecombo failure when I first tried this might be the same root cause. Digging into the envseetup source | 03:01:58 | |
Ok, I think I'm getting somewhere... Calling breakfast instead of choosecombo seems to do the trick. | 04:15:30 | |
| Sorry for spamming here. Please let me know if my level of messaging is inappropriate. | 04:15:46 | |
| This is what I'm currently working on:
| 04:16:30 | |
| Trying to figure out where the build system is getting that hash | 04:38:50 | |
Ahhhh, the radio files are using git lfs | 05:25:57 | |
Manually updated the vendor.json entry for cheetah setting fetchLFS to true to no effect. digging into why this is not working. | 05:50:46 | |
| did you update the hash? | 05:52:16 | |
| No, trying that now. | 06:03:24 | |
| overall, remember that Nix trusts you when you tell it what the hash of a thing is | 06:15:02 | |
| I pulled down the LFS repo, then realized I don't know what I should be hashing | 06:15:25 | |
| No idea how to get the hash for an LFS repo | 06:15:36 | |
| Better yet, how should the update_device_dirs.py script know that a repo has LFS files? I guess that would be specifically flagged similar to other devices with special cases? | 06:19:39 | |
Did the old trick of corrupting the hash to see what Nix would expect, and it still wants to old hash despite fetchLFS being true. | 06:24:21 | |
| the "old trick" is "TOFU"; trust on first use | 06:24:52 | |
| and yeah | 06:24:56 | |
| though I guess you need something else | 06:25:09 | |
| (haven't touched robotnix in a while) | 06:25:14 | |