| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
We are now installing properly named icons, no need to
rename anymore.
This was causing ci to fail.
|
| | |
|
| |
|
|
|
|
|
|
| |
Our flatpak-builder manifests include building Graphene from Git; since
we're building the GTK demos, it's pointless to build the Graphene tests
as well. Disabling tests and benchmarks avoids pointless installations
inside the Flatpak build repo that will just be removed by the time we
bundle the demo.
|
| |
|
|
|
| |
We need a newer wayland than is available in the runtime
currently, so use the power of flatpak and bundle it.
|
| |
|
|
|
| |
We can use manifests as targets when building GTK inside a flatpak
environment; or we can use them for CI purposes.
|
| |
|
|
|
|
|
| |
GIO has this facility, so we should use it.
At the same time, make sure the immodules directory
exists, even if we don't install any modules there
outselves.
|
| |
|
|
|
|
|
|
|
|
|
| |
Add an extension point called gtk-im-module, which requires
the type GtkIMContext. Simplify the loading by using GIO
infrastructure. Drop the locale filtering for now, I don't
think it is really necessary nowadays.
Convert existing platform modules to gio modules.
Sill to do: Drop the conditional build machinery.
Either always include them, or never.
|
| |
|
|
|
|
|
|
| |
Before running gtk-query-immodules, the cache output directory may not
actually exist. Make sure it does before we try to write into it.
https://bugzilla.gnome.org/show_bug.cgi?id=793182
Signed-off-by: Daniel Stone <daniels@collabora.com>
|
| |
|
|
|
| |
Use the appropriate variable when expanding the input method modules
path.
|
|
|
When building GTK+ straight from the repository without any assistance
from packaging tools, we need to trigger system-wide updates, like the
icon theme cache update, or the schema compilation.
|
