| 3 Jun 2024 |
 erahhal | I guess this is where I admit I should know more about using a nix development environment. How do I see where the sources are pulled down? I've been testing this by creating a flake that pulls in my robotnix branch as an input then calls robotnixSystem | 20:52:15 |
| erahhal | It seems that it's putting sources into the nix store during build time, but otherwise I don't know | 20:52:39 |
 atemu12 | It's actually constructing an android source tree in the build env | 20:53:05 |
| atemu12 | You can check the source.dirs attribute for the paths that will be linked and their sources | 20:53:24 |
| erahhal | Right, how do I do that though 😅 | 20:55:08 |
| erahhal | This is sort of a complicated project to be diving into as someone not very experienced with Nix build environment heh. But I guess I'm the type to learn by jumping into the deep end of the pool | 20:56:02 |
| erahhal | * This is sort of a complicated project to be diving into as someone not very experienced with Nix build environment heh. But I guess I'm the type to learn to swim by jumping into the deep end of the pool | 20:56:35 |
| atemu12 | You mean how to instrospect Nix values? | 20:56:54 |
| atemu12 | nix repl is a good start | 20:56:55 |
| atemu12 | In reply to @erahhal:matrix.org
This is sort of a complicated project to be diving into as someone not very experienced with Nix build environment heh. But I guess I'm the type to learn to swim by jumping into the deep end of the pool That's the spirit :) | 20:57:19 |
| erahhal | Ok, I'll do a bit of reading on how to use the repl | 20:58:06 |
| atemu12 | Just open the repl on robotnix and poke around | 20:58:28 |
| atemu12 | It'll try to print any value you give ti | 20:58:34 |
| atemu12 | * It'll try to print any value you give it | 20:58:39 |
| atemu12 | Robotnix is a module system, so the result of all the configuration is in the config attribute | 20:59:01 |
| atemu12 | Just like NixOS | 20:59:04 |
| erahhal | Ah, so not my personal flake. I'll try it directly on robotnix | 21:16:19 |
| erahhal | So I see /device/google/cheetah and /vendor/google/cheetah, and a bunch of dirs that start with kernel/*, but no kernel that is specific to the device. According to the dependency tree, the kernel is the pantah-kernel, but that was excluded above due to the nix error I mentioned before. | 21:26:37 |
| erahhal | I believe all gen 7 pixels are "pantah" devices | 21:27:21 |
| atemu12 | Does LOS support your device? | 21:34:39 |
| atemu12 | Is the device dir in the json? | 21:34:54 |
| atemu12 | Does its lineag.dependencies list the kernel dir? | 21:35:14 |
| atemu12 | * Does its lineage.dependencies list the kernel dir? | 21:36:06 |
| erahhal | definitely, I'm running LOS on it right now | 21:39:58 |
| erahhal | specifically 21 | 21:40:02 |
| erahhal | It does, pantah-kernel | 21:40:12 |
| erahhal | but I removed it above as it depended on gs101, which depends on gs-common | 21:40:46 |
| erahhal | which doesn't seem to have a vendor repo | 21:40:52 |
| erahhal | sorry, not true, it has the following deps: | 21:42:53 |
| erahhal | cheetah --> pantah --> pantah-kernel, and cheetah --> pantah --> gs201 --> gs101 --> gs-common | 21:43:36 |
