Le Wed, Nov 12, 2025 at 08:43:56PM +0100, Kirill A. Korinsky a écrit : > On Wed, 12 Nov 2025 20:23:07 +0100, > Landry Breuil <[email protected]> wrote: > > > > > > > > > > This feels... wrong. > > > > > > > > > > can't we somehow make it directly use the meson module with > > > > > gtk/meson.build, instead of their homegrown horror of > > > > > make/configure.py ? > > > > > > > > > > > > > this homegrown horror creates GNUmakefile which compiles some > > > > dependencies, > > > > and after it's done it calls meson and after that ninja. > > > > > > > > Before it was autoconf and make, but they decided to migrate to meson. > > > > > > > > Here a bit cleaner diff where I nuke autotools, and it survived a build > > > > in > > > > clean chroot. And I also put comment which explains why meson/ninja > > > > here. > > > > > > > > > > ...and I forgot to add new patches. Here the right diff. > > > > seems it switched to Gtk+4 :) > > > > Run-time dependency gtk4 found: YES 4.20.2 > > > > Thanks to catch it. I've regenerated WANTLIBS and it seems quite shorter > than it was before.
Yeah, thank meson for that.. anyway, i guess this is as good as it can get with that funky configure system... runs fine here, ok.
