Install gtk4 with Homebrew, apt, dnf, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• gtk4-builder-tool
• gtk4-demo
• gtk4-demo-application
• gtk4-encode-symbolic-svg
• gtk4-icon-editor
• gtk4-image-tool
• gtk4-launch
• gtk4-node-editor
• gtk4-path-tool
• gtk4-print-editor
• gtk4-query-settings
• gtk4-rendernode-tool
• gtk4-update-icon-cache
• gtk4-widget-factory

Project history

The GTK project site describes GTK as a free and open-source cross-platform widget toolkit maintained by GNOME and contributors, built on GLib, and suitable for applications ranging from small tools to application suites. The site also identifies GTK as hosted by GNOME and maintained by the GTK Team, with project copyright dating from 1997.

GTK's major-version history is visible through GNOME source tarballs and upstream migration documentation. GTK 2.0 source tarballs are published from March 2002; GTK 3.0 source tarballs are published from February 2011; and GTK 4.0 tarballs are published from December 2020. The GTK 4 migration guide explicitly treats GTK 4 as a new major version that breaks API and ABI compared with GTK 3.x, and recommends preparing applications from the final stable GTK 3.24 series.

GTK 4 development began as a multi-year effort around the 3.89.1 development release in November 2016. The GTK 4.0 release announcement says the 4.0 result came after more than 18,000 commits and more than 20 development releases, with major themes including render nodes, event controllers, layout managers, media playback, scalable lists, shaders, data transfers, and accessibility.

The gtk4 package role should be read as a version-track role, not a separate unrelated project. It packages the GTK 4 generation of the same toolkit lineage, alongside language bindings and applications that choose the GTK 4 API. The package's executables such as gtk4-demo, gtk4-widget-factory, gtk4-builder-tool, gtk4-launch, and gtk4-query-settings are developer and diagnostic tools around the library.

Adoption history

GTK's adoption is tied to GNOME but not limited to it. The GTK project site describes GTK as the core of the GNOME development platform and also suitable for other Linux environments plus Windows and macOS targets. Its homepage lists applications built with GTK such as GIMP, Inkscape, Evolution, Web, Calculator, Maps, Transmission, and others.

GTK 4 adoption started as a porting path for applications and platform libraries after the 4.0 release. The GTK 4.0 announcement called out GNOME 40 applications and adjacent libraries such as vte, WebKitGTK, and GtkSourceView as parts of the ecosystem that needed GTK 4 ports.

How it is used

Developers use GTK 4 by linking against the Gtk 4.0 API, using the official API reference and getting-started guides, and optionally using language bindings for C, JavaScript, Perl, Python, Rust, Vala, C++, and other languages. GTK applications are event-driven widget hierarchies, often assembled through code or GtkBuilder UI descriptions.

Packagers and developers use gtk4 command-line tools for demos, widget inspection, resource and UI conversion, icon cache updates, builder-file validation, launching applications, print testing, settings queries, render-node inspection, and visual experiments. Those tools make gtk4 a developer-platform package even when a desktop user sees it only as an application dependency.

Why package nerds care

gtk4 is one of the packages that defines a desktop stack. Its ABI, introspection metadata, demos, schemas, icons, input modules, themes, and build flags influence a large set of reverse dependencies, especially in GNOME and GTK language-binding ecosystems.

The package is also a marker of a major toolkit transition. GTK 4 changes rendering and input architecture compared with GTK 3, removes long-deprecated APIs, and requires applications and related libraries to make deliberate porting decisions. For package maintainers, it sits at the intersection of C ABI stability, GObject Introspection, Meson builds, platform backends, accessibility, and downstream application migration.

Timeline

• 1997: The GTK project site copyright range begins, reflecting the early GTK project era.
• 2002-03-08: GNOME publishes GTK+ 2.0.0 source tarballs.
• 2011-02-10: GNOME publishes GTK+ 3.0.0 source tarballs.
• 2016-11: The GTK 4.0 announcement identifies 3.89.1 as the development point after which the GTK 4 effort added more than 18,000 commits.
• 2020-12-16: GTK 4.0 is released and source tarballs are published.
• 2021-03: GNOME 40 is identified in the GTK 4.0 announcement as an early adoption target for GTK 4 applications.
• 2023-09: GNOME Translation Editor 45.1 records a GTK 4 and libadwaita migration, one example of downstream GTK 4 application porting.

Related projects

• GLib is the foundational utility and object-system library below GTK.
• GObject Introspection and language bindings allow GTK APIs to be used from several languages.
• GNOME is the primary desktop platform around GTK.
• vte, WebKitGTK, GtkSourceView, libadwaita, GIMP, Inkscape, Evolution, and GNOME applications are important ecosystem consumers or related libraries.

Sources

• https://blog.gtk.org/2020/
• https://blog.gtk.org/2020/12/16/gtk-4-0/
• https://docs.gtk.org/gtk4/
• https://docs.gtk.org/gtk4/migrating-3to4.html
• https://download.gnome.org/sources/gtk%2B/2.0/
• https://download.gnome.org/sources/gtk%2B/3.0/
• https://download.gnome.org/sources/gtk/4.0/
• https://www.gtk.org/
• https://www.gtk.org/docs/getting-started/index