| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
1.14.x series does not contain the functionality needed by GTK+.
Advise to use 1.15.x (1.15.2 is available) or 1.16.x (yet to be released).
https://bugzilla.gnome.org/show_bug.cgi?id=765790
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
So nautilus and other consumers of the sidebar can use the non
API-broken API of the sidebar.
|
|
|
|
| |
We need to drop the reference to it in configure.ac as well...
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Visual Studio, unlike MinGW, manifest files are embedded via
including the manifest file as a resource file in the projects, not
via the .rc file. This means that the line in the .rc file that
specifies the manifest file would cause trouble, so that line gets
removed when the full gtk3-win32.rc is generated on Visual Studio builds,
otherwise 2010+ Visual Studio will complain when compiling the .rc file.
Also, the inclusion of winuser.h will cause warnings during the
compilation of the .rc file.
Fix this by isolating the Win32 resource portions of gtk-win32.rc.in to
gtk-win32.rc.body.in and:
-On MinGW, construct the full gtk-win32.rc by doing the winver.h and
winuser.h inclusion first, then append the contents of gtk-win32.rc.body,
and then appending the line to embed the manifest file.
-On Visual Studio, simply copy the gtk-win32.rc.body to gtk-win32.rc,
and generate the full libgtk3.manifest file.
https://bugzilla.gnome.org/show_bug.cgi?id=762311
|
| |
|
| |
|
|
|
|
| |
The demo also uses PangoFt2 API.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The font features demo started calling the Harfbuzz API directly
starting from commit 9de3b24c205f1c647292a490f92f21a776b931a4. Harfbuzz
is an implicit dependency of Pango on some platforms, but it's not part
of the public dependencies; this means that we cannot expect to link to
Pango and automatically get Harfbuzz symbols to link against —
especially when things like --as-needed are in play.
This change triggered build failures on non-Unix platforms, fixed by
commit 2a9967731a3b77b102ada633c39b5a35efc80957, as well as build
failures in Continuous, with this error message:
/usr/lib/gcc/x86_64-gnomeostree-linux/4.9.3/../../../../x86_64-gnomeostree-linux/bin/ld:
font_features.o: undefined reference to symbol 'hb_tag_to_string'
//lib/libharfbuzz.so.0: error adding symbols: DSO missing from command
line
collect2: error: ld returned 1 exit status
In order to get the font features demo to build everywhere we should
take an explicit, though optional, check on Harfbuzz, and conditionally
build the font features demo with the right compiler and linker flags.
|
|
|
|
| |
Needed since commit 1045dda0358dee67e8dfbf13b40181b4c2ba1f1c
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This uses the same function for dumping CSS nodes and styles
as the CSS node test. It can be used to test aspects of inheritance
and matching, as well as initial values.
No actual tests yet.
|
|
|
|
| |
No actual tests yet.
|
|
|
|
|
| |
Also use MS variant of flockfile, if available
(requires MSVCRT compatible with MSVCR90 or newer).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of having our own copy of the pointer gestures XML file, use
the one installed by wayland-protocols.
Since pointer gestures is an unstable protocol, it went through the
unstable protocol naming convention changes, which is reflected in this
commit.
https://bugzilla.gnome.org/show_bug.cgi?id=758634
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Load /usr/share/X11/locale/$LOCALE/Compose and $HOME/.XCompose
dynamically.
https://bugzilla.gnome.org/show_bug.cgi?id=721120
|
|
|
|
| |
Otherwise, internal use of new API causes deprecation warnings.
|
| |
|
| |
|
|
|
|
|
| |
Use a different CFLAGS variable to carry them. I chose the DEBUG_FLAGS
because that's essentially what those flags are: debug helpers.
|
|
|
|
|
|
| |
GTK cannot depend on libcanberra-gtk which depends on GTK. This causes
a circular dependency and is especially neat if installed GTK is
different enough from uninstalled GTK.
|
|
|
|
|
|
| |
"Add" Visual Studio 2015 projects by what we did before: Copy the Visual
Studio 2010 project files and replace the items in there as needed, as
the formats of the 2010 and 2015 projects are largely the same.
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to rename the projects so that when these projects are added
into an all-in-one solution file that will build the GTK+ 2/3 stack,
the names of the projects will not collide with the GTK+-2.x ones,
especially as GTK+-2.x and GTK+-3.x are done to co-exist on the same
system. This is due to the case that the MSVC projects are directly
carried over from the GTK+-2.x ones and was then updated for 3.x.
We still need to update the GUIDs of the projects, so that they won't
conflict with the GTK+-2.x ones.
|
|
|
|
| |
Needed since 29c799a1e77e441160892366355e9a55aed5df40
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use a separate G_ENABLE_CONSISTENCY_CHECKS define to guard internal
consistency checks that are applied unconditionally if they are enabled,
such as the widget invariants checking. Interactive debug spew that can
be triggered at runtime with the GTK_DEBUG environment variable is still
guarded by the G_ENABLE_DEBUG define.
The mapping from enable-debug levels to defines is as follows:
yes: G_ENABLE_DEBUG G_ENABLE_CONSISTENCY_CHECKS
minimum: G_ENABLE_DEBUG G_DISABLE_CAST_CHECKS
no: G_DISABLE_CAST_CHECKS G_DISABLE_ASSERT G_DISABLE_CHECKS
|
| |
|
| |
|
|
|
|
|
|
|
| |
GTK+ now uses pango_attr_foreground_alpha_new, pango_attr_background_alpha_new,
PANGO_ATTR_FOREGROUND_ALPHA, PANGO_ATTR_BACKGROUND_ALPHA,
pango_renderer_set_alpha, pango_renderer_get_alpha, which were all added
after 1.37.2.
|
| |
|
|
|
|
|
| |
We don't use pangoft2 at all in libgdk, but we are using it in libgtk
both under X and Wayland.
|
|
|
|
|
| |
libcanberra calls x11 backend functions, so we can't use it
when the x11 backend is disabled.
|
|
|
|
|
|
|
|
| |
I invadvertendly introduced a dependency on a recent GLib recently,
by cherry-picking a fix that used new GLib API. This commit will
help catching such errors before release, by using the versioned
deprecation machinery to turn such events into build-time
warnings.
|
| |
|
| |
|
|
|
|
|
| |
The font features demo that was just added uses bleeding-edge
pango features.
|
| |
|