GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Emmanuele Bassi f353bbd0bc ci: Add two flatpak jobs
When building GTK through the CI infrastructure, it would help to have
some ways of testing it; for instance, if we want to verify that theme
changes are useful, or if we want to run the result without necessarily
build it locally.

This is where flatpak comes in handy. By having the CI build a flatpak
buundle, and storing it as an artifact, of the GTK demos, we can easily
point developers and designers to an installable binary that won't break
their system, nor will require development tools and environments to
run.
2018-03-20 23:14:32 +00:00
.gitlab-ci gitlab-ci: enable gtk+:gdk tests 2018-03-20 17:31:38 +01:00
build-aux Add flatpak builder manifests for our demos 2018-03-20 23:14:32 +00:00
demos Merge branch 'rename-window-to-surface' into 'master' 2018-03-20 16:16:57 +00:00
docs Convert all references to GdkEvent->surface 2018-03-20 16:25:50 +01:00
examples GtkWidget: Start renaming widget->window 2018-03-20 15:21:12 +01:00
gdk Merge branch 'detect-synaptics-touchpads-v2' into 'master' 2018-03-20 17:03:15 +00:00
gsk Merge branch 'rename-window-to-surface' into 'master' 2018-03-20 16:16:57 +00:00
gtk Merge branch 'rename-window-to-surface' into 'master' 2018-03-20 16:16:57 +00:00
modules gtk: Add a GStreamer implementation of GtkMediaFile 2018-03-18 21:01:23 +01:00
po Update POTFILES.in 2018-03-20 17:32:35 +01:00
po-properties Update POTFILES.in 2018-03-20 17:32:35 +01:00
subprojects Update the wrap file for GLib 2018-02-15 11:30:03 +00:00
tests tests: Update renamed symbol 2018-03-20 17:05:33 +00:00
testsuite Merge branch 'rename-window-to-surface' into 'master' 2018-03-20 16:16:57 +00:00
.gitlab-ci.yml ci: Add two flatpak jobs 2018-03-20 23:14:32 +00:00
AUTHORS
config.h.meson gtk: Add a GStreamer implementation of GtkMediaFile 2018-03-18 21:01:23 +01:00
CONTRIBUTING.md Update CONTRIBUTING.md 2018-03-13 18:13:46 +00:00
COPYING
gtk.doap Rename the project's DOAP file 2018-02-08 14:11:42 +00:00
gtk+-4.0.pc.in gtk+-4.0.pc: Make sure to add requirements for Gsk (e.g. graphene-1.0) 2016-10-27 08:21:13 +02:00
gtk+-unix-print-4.0.pc.in
make-pot make-pot: Make it executable 2017-08-15 16:30:14 +02:00
meson_options.txt build: Make GStreamer backend the default 2018-03-18 21:01:23 +01:00
meson.build mediafile: Turn into an extension point 2018-03-18 21:01:23 +01:00
NEWS Split NEWS 2018-01-10 19:06:45 -05:00
NEWS.pre-1.0 Split NEWS 2018-01-10 19:06:45 -05:00
NEWS.pre-2.0 Split NEWS 2018-01-10 19:06:45 -05:00
NEWS.pre-3.0 Split NEWS 2018-01-10 19:06:45 -05:00
README.commits
README.md README.md: Minor updates 2018-02-24 21:31:52 -05:00

GTK+ — The GTK toolkit

General information

GTK+ is a multi-platform toolkit for creating graphical user interfaces. Offering a complete set of widgets, GTK+ is suitable for projects ranging from small one-off projects to complete application suites.

GTK+ is free software and part of the GNU Project. However, the licensing terms for GTK+, the GNU LGPL, allow it to be used by all developers, including those developing proprietary software, without any license fees or royalties.

The official download location

The official web site

The official developers blog

Information about mailing lists can be found at

Building and installing

In order to build GTK+ you will need:

You will also need various dependencies, based on the platform you are building for:

If you are building the X11 backend, you will also need:

  • Xlib, and the following X extensions:
    • xrandr
    • xrender
    • xi
    • xext
    • xfixes
    • xcursor
    • xdamage
    • xcomposite
  • atk-bridge-2.0

If you are building the Wayland backend, you will also need:

  • Wayland-client
  • Wayland-protocols
  • Wayland-cursor
  • Wayland-EGL

Once you have all the necessary dependencies, you can build GTK+ by using Meson:

$ meson _build .
$ cd _build
$ ninja

You can run the test suite using:

$ meson test

And, finally, you can install GTK+ using:

$ sudo ninja install

Complete information about installing GTK+ and related libraries can be found in the file:

docs/reference/gtk/html/gtk-building.html

Or online

How to report bugs

Bugs should be reported to the GNOME bug tracking system. You will need an account for yourself.

In the bug report please include:

  • Information about your system. For instance:

    • which version of GTK+ you are using
    • what operating system and version
    • for Linux, which distribution
    • if you built GTK+, the list of options used to configure the build

    And anything else you think is relevant.

  • How to reproduce the bug.

    If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.

  • If the bug was a crash, the exact text that was printed out when the crash occurred.

  • Further information such as stack traces may be useful, but is not necessary.

Contributing

Patches should also be submitted to the bug tracking system. If the patch fixes an existing bug, add the patch as an attachment to that bug report; otherwise, enter a new bug report that describes the patch, and attach the patch to that bug report.

Patches should be in Git-formatted form. You should use git format-patch to generate them. We recommend using git-bz.

For more information on the recommended workflow, please read this wiki page.

Please, follow the CODING_STYLE document in order to conform to GTK+'s coding style when submitting a code contribution.

Release notes

The release notes for GTK+ are part of the migration guide in the API reference. See:

Licensing terms

GTK+ is released under the terms of the GNU Lesser General Public License, version 2.1 or, at your option, any later version, as published by the Free Software Foundation.

Please, see the COPYING file for further information.