| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
We pin GLib, so we must also pin g-i to the same version, otherwise
we'll get weird mismatches during development.
|
|
|
|
|
| |
This commit has fixes for subproject use that we need,
and is not in a release yet.
|
| |
|
|
|
|
|
|
| |
We need recent fixes for graphene subproject use,
so use the current HEAD of master until there is
a release with these fixes.
|
|
|
|
|
|
| |
We need recent fixes for graphene subproject use,
so use the current HEAD of master until there is
a release with these fixes.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We don't want to use cairo 1.16, since it is
too old, so use 1.17.6 for now until there
is a stable 1.18 release.
|
|
|
|
| |
This is the latest stable release.
|
|
|
|
|
|
|
|
| |
Dummy dependencies are not required to execute a subproject
automatically for providing a program, nor do you need to explicitly
call subproject() to do that.
A `[provide]` section in the wrap file is enough.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Subprojects that use meson.override_dependency() do not require the
caller to provide the dependency variable name inside the subproject.
We also don't want to provide the *subproject* name, because the
subproject name can be `pango-1.50.12` instead of `pango` when using
wrap-file to download the tarball instead of using wrap-git. This
causes the pango subproject to be executed twice when using gtk as
a subproject inside gstreamer (which uses pango-1.50.12 as
a wrap-file).
All the dependencies we use can be switched in this way, but the
remaining ones need to be changed to use meson.override_dependency()
first.
|
|
|
|
|
| |
Also switch the wrap file style to use spaces around `=` which is the
canonical style used by wrapdb now.
|
|
|
|
|
| |
We don't need the latest harfbuzz.
Stick to 4.0 for now.
|
| |
|
|
|
|
|
| |
We are using Harfbuzz api in the file chooser,
so lets make this official.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the hotspot of DND surfaces work when using the Vulkan and
OpenGL renderers.
This bumps the CI image used to the newly built image. This is needed to
install a new enough libwayland-client.so needed for wl_surface.offset.
This is done by adding wayland as a meson subproject, building it
on-demand if the version in the system is not new enough. As
libwayland-client.so is pulled in implicitly when linking to gtk4, the
compile step needs LD_LIBRARY_PATH set to make ld find the right library
to link to.
|
|
|
|
| |
see https://github.com/mesonbuild/wrapdb/pull/171
|
|
|
|
|
|
|
|
| |
Add support for the tiff format, which is flexible
enough to handle all our memory texture formats
without loss.
As a consequence, we are now linking against libtiff.
|
|
|
|
|
|
|
|
|
| |
Using libpng instead of the lowest-common-denominator
gdk-pixbuf loader. This will allow us to load >8bit data,
and apply gamma and color correction in the future.
For now, this still just provides RGBA8 data.
As a consequence, we are now linking against libpng.
|
|
|
|
|
|
|
| |
Change the Pango subproject to use the main branch.
This depends on
https://gitlab.gnome.org/GNOME/pango/-/merge_requests/379
|
|
|
|
|
|
|
|
| |
GLib upstream has renamed its `master` branch to `main`.
See https://gitlab.gnome.org/GNOME/glib/-/issues/2348.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
|
|
|
|
| |
This protocol implements the IPC necessary to focus application
windows across launcher/launchee. Add support for it.
|
|
|
|
| |
Do not use my personal workspace.
|
|
|
|
| |
No longer used.
|
|
|
|
|
| |
While we're developing gi-docgen it's better to have it as part of our
build.
|
|
|
|
|
|
| |
This reverts commit 710ef00dfea4853d99e1c7f7201733d81d2b846d.
The cairo change has been merged.
|
|
|
|
|
|
|
| |
Change the subproject to point to a branch that includes
an OS X build fix. Once
https://gitlab.freedesktop.org/cairo/cairo/-/issues/441
is fixed, we should switch back to master.
|
|
|
|
|
|
|
|
|
| |
There is no reason to fallback to find_library for cairo and still rely
on pkg-config for all other dependencies, and just when using MSVC. When
building and pkg-config is not working it is preferable to fallback to a
subproject just like for all other dependencies.
Also add cairo.wrap now that meson support has been merged upstream.
|
|
|
|
|
| |
I've merged the relevant parts from the gtk-doc-for-gtk4
branch.
|
|
|
|
| |
This helps reduce bandwidth requirements for ci.
|
|
|
|
|
|
|
|
| |
Sysprof has moved to a new ABI which removes GLib from the capture library
so that GLib itself can link against sysprof-capture.
This bumps the library ABI so we can keep things coordinated between all
the new tracing layers in the stack.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To build a better world sometimes means having to tear the old one down.
-- Alexander Pierce, "Captain America: The Winter Soldier"
ATK served us well for nearly 20 years, but the world has changed, and
GTK has changed with it. Now ATK is mostly a hindrance towards improving
the accessibility stack:
- it maps to a very specific implementation, AT-SPI, which is Linux and
Unix specific
- it requires implementing the same functionality in three different
layers of the stack: AT-SPI, ATK, and GTK
- only GTK uses it; every other Linux and Unix toolkit and application
talks to AT-SPI directly, including assistive technologies
Sadly, we cannot incrementally port GTK to a new accessibility stack;
since ATK insulates us entirely from the underlying implementation, we
cannot replace it piecemeal. Instead, we're going to remove everything
and then incrementally build on a clean slate:
- add an "accessible" interface, implemented by GTK objects directly,
which describe the accessible role and state changes for every UI
element
- add an "assistive technology context" to proxy a native accessibility
API, and assign it to every widget
- implement the AT context depending on the platform
For more information, see: https://gitlab.gnome.org/GNOME/gtk/-/issues/2833
|
|
|
|
| |
Very similar to the other fallbacks we use.
|
|
|
|
|
|
|
| |
We don't really need the full history and branches when building
sub-projects.
This should shave some bandwidth and time in our CI pipeline as well.
|
|
|
|
|
| |
We require a new version of libcloudproviders so that we can enable it
in our CI pipeline.
|
|
|
|
|
| |
This branch contains assorted fixes and enhancements that
are needed to build the gtk4 docs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The third version of xdg-shell introduces support for explicit popup
repositioning. If available, make use of this to implement popup
repositioning.
Note that this does *NOT* include atomic parent-child state
synchronization. For that,
https://gitlab.freedesktop.org/wayland/wayland-protocols/issues/13 will
be needed.
This currently uses my own fork of wayland-protocols which adds meson
support, so that we can use it as a subproject. Eventually when
wayland-protocols' meson support lands upstream, we should change it to
point there.
Silence some meson warnings while at it to make CI happy.
This also bumps the glib requirement, since g_warning_once() is used.
|
|
|
|
| |
Using origin/master crashes meson.
|
|
|
|
|
|
|
|
|
|
| |
Instead of requiring sassc to be installed add meson subprojects
which build libsass and sassc (currently both forks of mine, tested
under linux/mingw/msvc) when needed.
This allows us to drop the generated .css files and build scripts from git.
See #1502
|
|
|
|
|
|
| |
We rely on a specific minimum version of gtk-doc to be able to build the
GTK API reference for the new API. In order to be able to use gtk-doc as
a subproject, though, we need to use a recent version of Meson.
|
|
|
|
| |
See: https://gitlab.gnome.org/GNOME/gtk/issues/1219
|
|
|
|
|
| |
Point to the right repo, now that GLib is on GitLab, instead of relying
on the redirection.
|
|
|
|
|
|
|
|
|
|
|
| |
With these changes gtk+ builds for me using fallbacks for all libraries
with fallbacks available. Needs the following changes:
https://github.com/ebassi/graphene/pull/109 (graphene)
https://bugzilla.gnome.org/show_bug.cgi?id=787414 (pango)
https://github.com/mesonbuild/meson/pull/2291 (will be in meson 0.42.1)
https://bugzilla.gnome.org/show_bug.cgi?id=787416
|
|
|
|
|
| |
Like we do for Graphene, we can build libepoxy as a sub-project of GTK+
in case we do not find the dependency installed on the system.
|
|
|