After several years of being in an unusually
unstable state, gtkmm-4.0 and gtk4 have now stabilized.
Application programmers can build them from tarballs or from git
clones. I assume that they will be available in Linux
distributions in due time.
gtkmm-4.0 depends on new releases of several other C++ packages, parallel installable with similar older packages.
Columns in table:
A. ABI name of package used by gtkmm-4.0
B. Tarball name of latest version
C. ABI name of similar package used by
gtkmm-3.0
ABI = Application Binary Interface; ABI names are the names of
pkg-config's .pc files.
| A. ABI name 4 |
B: Tarball name |
C: ABI name 3 |
| sigc++-3.0 |
libsigc++-3.0.6.tar.xz |
sigc++-2.0 |
| cairomm-1.16 |
cairomm-1.16.0.tar.xz |
cairomm-1.0 |
| glibmm-2.68 giomm-2.68 |
glibmm-2.68.0.tar.xz |
glibmm-2.4 giomm-2.4 |
| (atkmm-2.36) |
(atkmm-2.36.0.tar.xz) |
atkmm-1.6 |
| pangomm-2.48 |
pangomm-2.48.0.tar.xz |
pangomm-1.4 |
| gtk4 |
gtk-4.0.0.tar.xz |
gtk+-3.0 gdk-3.0 |
| gtkmm-4.0 |
gtkmm-4.0.0.tar.xz |
gtkmm-3.0 gdkmm-3.0 |
gtkmm-4.0 does not depend on atkmm. You don't
need atkmm in order to build and run gtkmm-4.0.
There is no gdkmm-4.0 ABI.
All these packages can be built with Meson. If you build from git clones, you also need mm-common.
There is a version of the gtkmm tutorial that
describes gtkmm-4.0, https://developer.gnome.org/gtkmm-tutorial/4.0