mobile-nixos VS naersk

For now, only information about Ubuntu Touch support is available on our website. We plan to extend that to PostmarketOS and NixOS. But which devices does Ubuntu Touch support? For example those:

Github has more recent activity: https://github.com/NixOS/mobile-nixos

NixOS/mobile-nixos

Any nixos users here? Anyone have any luck running mobile nixos?

samueldr has been doing a lot of work in that direction. See https://mobile.nixos.org/

With the code from https://github.com/NixOS/mobile-nixos/pull/445, build the demo example with nix-build --argstr device pine64-pinephonepro -A outputs.temp-tow-boot-install-script examples/demo/; of course instead of example/demo you can have your own configuration, but I started with demo

https://github.com/NixOS/mobile-nixos/pull/361

Though you might want to ask around for your particular use case. While basic support (it boots) is right around the corner, it's probably not yet at a point where it'll be nice to use.

As for what I did with those zip files? I made the equivalent for another Linux on Android devices distro. The implementation probably won't suit your tastes, but it's something else to look at to figure out what can be done.

i would also recommend using crane or naersk since iirc rustPlaform.buildRustPackage can mangle some of these options (or maybe i just did something wrong lol)

Have a look at naersk, it neither requires generated Nix files nor IFD.

We use naersk[0] for Rust projects in our Nix monorepo (for example [1]). It's pretty hands-off in terms of the Nix code needed (you don't need to pin hashes inside of the Nix code as long as you have a Cargo lockfile) and all the existing tooling keeps working fine.

The main drawback of it is that it currently builds all of your dependencies in one big derivation, so any dependency changes cause a full rebuild. There's some other project I saw fly by which attempts to do a similar thing but split each crate into a separate derivation, but I forgot what it's called and have no experience with it.

[0]: https://github.com/nix-community/naersk

[1]: https://cs.tvl.fyi/depot/-/blob/ops/journaldriver/default.ni...

You can also use naersk¹ if you want to avoid a two-step process. It's especially convenient when using nix flakes.

¹https://github.com/nix-community/naersk

I created https://github.com/nmattia/napalm/issues/34 and https://github.com/nmattia/naersk/issues/183 to move them to nix-community

sounds exactly like what naersk does. naersk doesn't need a cargSha256 argument since it downloads dependencies from Cargo.lock. it can also grab the version number from Cargo.toml