| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Otherwise we rely on whatever it's inside the PATH.
|
|
|
|
| |
- avoid vulkan from crashing the inspector
|
|
|
|
|
|
| |
- avoid using the selected blue for the sidebar
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/1586
|
|
|
|
|
|
| |
The pkg-config variables have been added in GLib 2.62.0. Let's fallback
to default names for these tools in such case (`pkg-config` still
returns a 0 return value, but with empty output for absent variables).
|
|
|
|
|
|
|
| |
Some distributions are renaming Glib/GIO utilities for multi-arch
reasons so pkg-config variables have been added to find the correct name
of a tool. GTK+ should use these variables instead of searching in PATH.
See glib#1796.
|
|
|
|
|
| |
This is what the ci is set up to use, and building
against 3.34 fails there.
|
|
|
|
|
|
|
| |
Downloading the subproject during the GTK build fails
in a flatpak build due to lack of network access.
flatpak-builder insists on having these things explicitly
spelled out as dependencies.
|
|
|
|
| |
And build it in ci.
|
|
|
|
|
|
|
|
| |
We are building against the 3.32 sdk, which has
a new-enough glib to default to the keyfile
settings backend.
Also, use fallback-x11, so we prefer Wayland.
|
| |
|
| |
|
|
|
|
|
|
| |
I was building GTK in a minimal container without
GTK3 installed, and this caused install to fail.
We should use the tool that we just installed.
|
| |
|
|
|
|
| |
Python APIs accept both `\` and `/` as path separators.
|
|
|
|
|
|
|
|
|
| |
While *some* systems alias python to python3 nowdays, this is
not true for eveything. Especially systems that can potentially
offer both python2 and python3.
According to both PEP 394 and PEP 441 its recommended to always
add the 3 in the shebang.
|
|\
| |
| |
| |
| | |
GTK+ 4: Improve Windows/Visual Studio build experience
See merge request GNOME/gtk!185
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The existing post-install shell script will most likely not work on
Visual Studio builds as there is normally no shell interpreter installed
on the system where the build is done, but the build is normally done in
a standard Windows cmd.exe console.
Instead, use a Python script so that it will work on the platforms that
Python supports.
|
|/
|
|
|
|
|
| |
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.
|