| 25 Nov 2024 |
 oak 🏳️🌈♥️ | Few weeks ago when I started looking at things, the first thing I tried to fix was the webview thing but then I just disabled it because I was told it is broken :D but then the errors I saw were related to something like when you upgrade nixpkgs and have too new versions of tools, for example the Python build scripts used features that were already removed from Python 3.11 | 00:15:36 |
| oak 🏳️🌈♥️ | * Few weeks ago when I started looking at things, the first thing I tried to fix was the webview thing but then I just disabled it because I was told it is broken :D but the errors I saw were related to something like when you upgrade nixpkgs and have too new versions of tools, for example the Python build scripts used features that were already removed from Python 3.11 | 00:16:03 |
| oak 🏳️🌈♥️ | Okay, it looks like the build process and build scripts of the webview are even more complex than the Android itself :D | 00:38:43 |
| oak 🏳️🌈♥️ | * Okay, it looks like the build process and build scripts of the webview are even more complex than the stuff for Android itself :D | 00:38:58 |
| oak 🏳️🌈♥️ | This seems to be another rabbit hole | 00:52:32 |
| oak 🏳️🌈♥️ | Apparently something has changed inside the Chromium build scripts because the mk-vendor-file.py script works for the old version but not for the newest version | 00:53:49 |
 Atemu | I really don't know, I've never ever touched that stuff | 01:25:13 |
| oak 🏳️🌈♥️ | Pain, they have added their own "vpython3" distirbution to the depot_tools of Chromium, I tried updating depot_tools since it was from 2020 | 02:54:36 |
| oak 🏳️🌈♥️ | Maybe it is possible to get it working if I autoPatchelf the binaries or something | 02:55:23 |
| oak 🏳️🌈♥️ | Or try to create similar Python environment with Nix and then patchShebangs | 02:57:30 |
| Atemu | I thought chromium was built inside of an FHS container? | 02:58:52 |
| Atemu | Like the android build? | 02:59:00 |
| oak 🏳️🌈♥️ | Can I use normal dynamic linking if I create FHS shell? | 02:59:33 |
| Atemu | Yup | 02:59:52 |
| Atemu | That's what it's for | 02:59:57 |
| oak 🏳️🌈♥️ | That's a thing to try tomorrow | 03:00:21 |
| oak 🏳️🌈♥️ | This mk-vendor-file.py calls some depot_tools/gclient.py flatten --pin-all-deps tool, and it seems to use some bundled "vpython3" tool, which is a virtualenv + some version of Python3 I think | 03:01:55 |
| oak 🏳️🌈♥️ | And they extensively do just call the process vpython3 everywhere | 03:02:41 |
| oak 🏳️🌈♥️ | They expect to find executable vpython3 in PATH | 03:03:10 |
| oak 🏳️🌈♥️ | They had repo tool, but then they had to write different tool for Chromium project | 03:04:05 |
 ryantrinkle | What's the smoothest phone and android to use with robotnix these days? | 16:58:52 |
| ryantrinkle | like, least likely to run into issues with building, updating, etc. | 16:59:16 |
| ryantrinkle | i'm on graphene now, but haven't updated in a long time | 16:59:35 |
 @samueldr:matrix.org | if you read the past few days' chatter, those that got built for and installed are likely those that fit your criteria... | 17:12:26 |
| @samueldr:matrix.org | ... but also I would presume that any that are currently well-supported by LineageOS in one of the supported release are almost just as likely to work well | 17:13:00 |
| @samueldr:matrix.org | (IIRC the previously mentioned phones were a fairphone, 4 IIRC? and oneplus 5?(T?)) | 17:13:41 |
| @samueldr:matrix.org | or uh... hmmm... lol https://github.com/nix-community/robotnix/blob/master/flavors/lineageos/supported_devices.toml | 17:14:47 |
| @samueldr:matrix.org | ah right, instantnoodle is oneplus 8 https://github.com/nix-community/robotnix/pull/258 | 17:15:27 |
| @samueldr:matrix.org | * ah right, instantnoodle is oneplus 8
| 17:15:38 |
| oak 🏳️🌈♥️ | Depends on what you want to run, I'd say if you want to run LineageOS then those devices supported by LineageOS are easy go | 21:00:13 |
