| 1 Dec 2025 |
 alexfmpe | * Those two commands mean
eval = aarch64-darwin
build = aarch64-linux
host = aarch64-linux
eval = aarch64-darwin
build = x86_64-linux
host = aarch64-linux | 18:40:11 |
 K900 | Eval should not matter at all | 18:40:34 |
| K900 | Anyway, the NDK does not in fact have aa64 host tools | 18:40:43 |
| K900 | So yes | 18:40:50 |
| alexfmpe | right, I'm just clarifying where 'darwin' fits in | 18:41:00 |
 emily | no AArch64 surprises me. you can't do Android dev on AArch64 Chromebooks? | 18:52:47 |
| K900 | You can't even run an IDE on those | 18:55:46 |
| K900 | Can you | 18:55:49 |
| emily | sure you can | 20:05:35 |
| emily | they have built-in Linux VMs with full graphical Wayland app support | 20:05:42 |
| emily | Android Studio is explicitly supported on the Intel ones at least | 20:05:50 |
| emily | no idea about the ARM ones but it'd surprise me if not | 20:05:57 |
| 2 Dec 2025 |
 DavHau | Occasionally I encounter cross packages which simply compile binaries for the wrong platform.
Is there a hook in nixpkgs that I can use to check if all binaries in $out/bin are for the correct platform? | 06:43:18 |
