Thanks for putting this together.

I would not like to see autotools support dropped until we can guarantee a good experience for all of our supported platforms: https://wiki.gnome.org/Projects/GLib/SupportedPlatforms. That includes the ones listed under ‘we want to set up regular testing for these’.

We discussed this at the GTK+ hackfest today, and in conclusion:
 - We’d like to target this metabug to be fixed for 2.58
 - We’d then keep the autotools and meson build systems in parallel for at least one release, but push for people to use meson where possible
 - In particular, we’d like to be sure that Windows, OS X, one of the BSDs, and the major Linux distributions all build GLib OK using meson
 - Once we’re satisfied that we have no regressions (and no later), we can drop autotools

It makes sense, yes. That's also the scenario/schedule I had in mind. Hopefully it will match the release of GTK4 that already dropped autotools.

The next step I was trying to achieve is getting glib 2.56 built with Meson in Cerbero for GStreamer 1.16. That should give us a lot of testing for cross-build and less usual platforms.

(In reply to Xavier Claessens from comment #3)
> It makes sense, yes. That's also the scenario/schedule I had in mind.
> Hopefully it will match the release of GTK4 that already dropped autotools.

There’s going to be no explicit synchronisation between GLib and GTK+ in migrating to Meson and dropping autotools.

> The next step I was trying to achieve is getting glib 2.56 built with Meson
> in Cerbero for GStreamer 1.16. That should give us a lot of testing for
> cross-build and less usual platforms.

That would be fantastic! Please keep this metabug updated with your findings.

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1306.