On Sat, Aug 17, 2024 at 11:01:06PM +0200, Andrea Pappacoda wrote: > I don't know much about glib2.0, especially when it comes to cross > compiling, but I have a suggestion regarding meson and ninja-build in > particular. > > I maintain the muon package, which is a C re-implementation of Meson. The > thing that might be useful to you is that it does not require python3 to > run, and while it currently depends on ninja-build as well, it can be built > with built-in samu support, which is a ninja re-implementation. I haven't > enabled that option since in Debian we already have ninja-build, and I > haven't saw a use case for it before now. > > Please let me know if this could help. I'm willing to make changes to muon > packaging in order to help you with your bootstrapping efforts. After all, > muon's raison d'être is portability.
glib2.0 certainly is not the simplest of packages when it comes to meson use. The trivial approach of replacing meson yields: err unknown option '--wrap-mode=nodownload' That's the third option passed to meson of many. I don't think this is feasible with reasonable effort, but I'm happy to let you prove me wrong about this. Unrelated to this, I sent patches for libxt #1078927 and cdebconf #1078936 to make their libglib2.0-dev dependencies optional. libverto doesn't just work in a similar way though. Helmut
