View Single Post
Old 03-27-2021, 10:37 PM   #177
NiMa
Fanatic
NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.NiMa ought to be getting tired of karma fortunes by now.
 
NiMa's Avatar
 
Posts: 507
Karma: 2390534
Join Date: Jun 2020
Location: Somewhere in the Universe
Device: Kobo Libra, Glo HD, Touch C/B, Mini, Glo, Aura SE, Clara HD, KT
Quote:
Originally Posted by NiLuJe View Post
@sherman: I've never felt any inclination for the qemu approach myself, but, IIRC, it's been done in the past, I think?

(In which case: all hail BuildRoot \o/).

ct-ng can do cross-native & canadian builds, but since BR handles cross ct-ng TCs, and can build TCs itself, ct-ng -> BR ought to be enough to get you a sysroot with another TC inside.
Might need some minor packaging shenanigans in BR to match the glibc, but that's it.

The TL;DR being: if you intend to build a sysroot, I highly recommend letting BuildRoot handle the heavy lifting (and, as far as I'm concerned, it has the advantage of supporting crosstool-ng TCs without any fuss.
BuildRoot worked like magic with my InkBox/Alpine setup where I needed a chroot environnement with glibc instead of musl
Also, creating a 'shippable' firmware is not that difficult; even diagnostics and recovery in InkBox were not that hard, and once you get the thing working, it likely will not fail for a long time
NiMa is offline   Reply With Quote