summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* 3.19.23.19.2Matthias Clasen2015-11-201-1/+1
|
* 3.19.1Matthias Clasen2015-10-271-1/+1
|
* mir: add mircookie as a dependencyWilliam Hua2015-10-151-1/+2
|
* GtkIMContextSimple: Load locale compose tables dynamically.Takao Fujiwara2015-10-091-0/+9
| | | | | | | Load /usr/share/X11/locale/$LOCALE/Compose and $HOME/.XCompose dynamically. https://bugzilla.gnome.org/show_bug.cgi?id=721120
* Bump version to 3.19.0Matthias Clasen2015-10-031-3/+3
| | | | Otherwise, internal use of new API causes deprecation warnings.
* 3.18.1Matthias Clasen2015-10-031-2/+2
|
* 3.18.03.18.0Matthias Clasen2015-09-211-2/+2
|
* configure: Don't put glib version flags into pc filesBenjamin Otte2015-09-211-1/+2
| | | | | Use a different CFLAGS variable to carry them. I chose the DEBUG_FLAGS because that's essentially what those flags are: debug helpers.
* widget-factory: Remove libcanberra supportBenjamin Otte2015-09-211-38/+0
| | | | | | 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.
* MSVC Builds: "Add" Visual Studio 2015 ProjectsChun-wei Fan2015-09-151-0/+1
| | | | | | "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.
* MSVC Builds: Massive Rename of ProjectsChun-wei Fan2015-09-151-2/+2
| | | | | | | | | | | | 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.
* configure: Require glib >= 2.45.8Rico Tzschichholz2015-09-151-2/+2
| | | | Needed since 29c799a1e77e441160892366355e9a55aed5df40
* 3.17.93.17.9Matthias Clasen2015-09-141-1/+1
|
* Introduce G_ENABLE_CONSISTENCY_CHECKSMatthias Clasen2015-09-091-1/+1
| | | | | | | | | | | | | | 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
* 3.17.83.17.8Matthias Clasen2015-09-021-1/+1
|
* 3.17.73.17.7Matthias Clasen2015-08-171-1/+1
|
* Bump Pango requirement to 1.37.3Christoph Reiter2015-08-161-1/+1
| | | | | | | 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.
* 3.17.63.17.6Matthias Clasen2015-08-051-1/+1
|
* Fix x11-less buildMatthias Clasen2015-07-261-4/+1
| | | | | We don't use pangoft2 at all in libgdk, but we are using it in libgtk both under X and Wayland.
* Don't use libcanberra without XMatthias Clasen2015-07-251-0/+4
| | | | | libcanberra calls x11 backend functions, so we can't use it when the x11 backend is disabled.
* Use versioned deprecations more seriouslyMatthias Clasen2015-07-211-2/+14
| | | | | | | | 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.
* 3.17.53.17.5Matthias Clasen2015-07-211-1/+1
|
* 3.17.43.17.4Matthias Clasen2015-06-231-1/+1
|
* Bump Pango requirementMatthias Clasen2015-06-191-1/+1
| | | | | The font features demo that was just added uses bleeding-edge pango features.
* configure: test have_docbook_style != yes, not have_docbook_dtdAlexander Larsson2015-06-171-1/+1
|
* configure: Require pango >= 1.37.0Rico Tzschichholz2015-06-021-1/+1
| | | | Needed since 049cbc8b74aa7a6fff1627c8c65cbfd3c86dfde8
* 3.17.33.17.3Matthias Clasen2015-05-271-1/+1
|
* 3.17.23.17.2Matthias Clasen2015-05-261-2/+2
|
* gtk3: add randr 1.5 monitor supportDave Airlie2015-05-211-0/+3
| | | | | | | | | | | | | | This patch introduces support for using the newly introduced monitor objects in the XRandR protocol. These objects are meant to be used to denote a set of rectangles representing a logical monitor, and are used to hide details like monitor tiling and virtual gpu outputs. This uses the new objects instead of crtc/outputs objects when they are available to create the monitor lists. X server 1.18 is required on the server side for randr 1.5. https://bugzilla.gnome.org/show_bug.cgi?id=749561
* configure.ac: Pull gio-unix dependency for all unix buildsMarco Trevisan (Treviño)2015-05-141-11/+5
| | | | | | | It's now needed by gtk-launch, so it's just the case to enable it for all the builds except the win32 one, instead of adding it for every unix backend. https://bugzilla.gnome.org/show_bug.cgi?id=744086
* Revert "Work around a pkg-config bug"Matthias Clasen2015-05-101-2/+1
| | | | | | | This reverts commit 57751fa391fce8b9f208c41260e8968dd4cdc800. I've been told that this is not, in fact, a pkg-config bug, but a pkg-config feature.
* gtk-builder-tool: Add some testsMatthias Clasen2015-05-021-0/+1
|
* Enable RGBA windows on W32Руслан Ижбулатов2015-04-291-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Requires Vista and newer. * Create surfaces with cairo_win32_surface_create_with_format * Provide an rgba visual that can be distinguished from the system visual * Make rgba visual the best available visual * Enable alpha-transparency for all windows that we control * Check for appropriate cairo capabilities at configure time (W32 - 1.14.3 newer than 2015-04-14; others - 1.14.0) * Check for composition support before enabling CSDs * Re-enable transparency on WM_DWMCOMPOSITIONCHANGED Windows that were created while composition was enabled and that were CSDed as a result and will look ugly (thick black borders or no borders at all) once composition is disabled. If composition is enabled afterwards, they will return back to normal. This happens, for example, when RDP session is opened to a desktop where a GTK application is running. For W7/Vista windows will only re-gain transparency after the RDP session is closed. For W8 transparency will only be gone momentarily. Windows that were created while composition was disabled will not be CSDed automatically and will use SSD (WM decorations), while windows that are CSDed manually will get a thin square border. If composition is enabled afterwards, these windows will not change. This is most noticeable for system menus (popup menus are often generated on the fly, system menus are created once) and some dialogues (About dialogue, for example). https://bugzilla.gnome.org/show_bug.cgi?id=727316
* 3.17.13.17.1Matthias Clasen2015-04-291-2/+2
|
* build: Avoid xgettext crash on MSYS2Daiki Ueno2015-04-271-1/+1
| | | | | | | | | | | | | | | isatty() on MSYS2 returns non-zero if the fd is stdout and is redirected to /dev/null. That lets xgettext to produce colorized output and leads to an assertion failure during terminal type detection. Although the problem should be fixed in MSYS2, isatty() could behave wrongly in many ways on Windows. Since gtk+ doesn't need colorized output, it would be safer to bypass the terminal dependent code. See also: https://lists.gnu.org/archive/html/bug-gettext/2015-04/msg00004.html https://bugzilla.gnome.org/show_bug.cgi?id=748346
* gdk-win32: Really Implement GdkScreen->is_composited()Chun-wei Fan2015-04-171-1/+1
| | | | | | | | | | | | | | | | | The current GdkScreen->is_composited() is a stub as we were having Windows XP being supported, which does not support Desktop Window Manager (DWM), which is used by Windows for composition. Windows Vista and later support DWM, and it is always enabled on Windows 8/ Server 2012 and later. Please note that as we are dropping XP support in this cycle, this is the commit that would say goodbye to Windows XP support for GTK+-3.x, by linking directly to dwmapi.dll. This means, we only check whether we are on Windows 8 or Server 2012 (or later) to see whether we unconditionally have composition enabled. https://bugzilla.gnome.org/show_bug.cgi?id=741849
* configure: specify that mir backend needs gio-unixDaniel van Vugt2015-04-151-0/+1
|
* make libcanberra support optionalAntoine Jacoutot2015-03-281-3/+27
| | | | | | | Make it possible to control libcanberra support so we don't risk ending up with a cyclic dependency when using packages: gtk+ -> libcanberra-gtk3 -> gtk+ https://bugzilla.gnome.org/show_bug.cgi?id=746904
* Start 3.17 developmentMatthias Clasen2015-03-221-2/+2
| | | | Bump the version to 3.17.0 and add version macros.
* 3.15.123.15.12Matthias Clasen2015-03-161-1/+1
|
* 3.15.113.15.11Matthias Clasen2015-03-121-1/+1
|
* Modernize the xReply checkMatthias Clasen2015-03-071-16/+10
| | | | | | | Using AC_CHECK_TYPE instead of AC_TRY_COMPILE avoids compiler warnings from -Werror. https://bugzilla.gnome.org/show_bug.cgi?id=535929
* Check for existence of sincosMatthias Clasen2015-03-041-1/+1
| | | | | | It apparently doesn't exist everywhere. https://bugzilla.gnome.org/show_bug.cgi?id=745578
* 3.15.103.15.10Matthias Clasen2015-03-021-1/+1
|
* Avoid stray output from configureMatthias Clasen2015-03-021-1/+1
| | | | The new xgettext check was leaving a messages.po file behind.
* Add a configure check for new enough gettextMatthias Clasen2015-02-261-0/+9
| | | | Check that xgettext understands glade files.
* Stop building extract-stringsMatthias Clasen2015-02-261-2/+0
| | | | It is no longer needed.
* 3.15.93.15.9Matthias Clasen2015-02-241-1/+1
|
* 3.15.83.15.8Matthias Clasen2015-02-201-1/+1
|
* Bump versionMatthias Clasen2015-02-131-1/+1
| | | | So apps can require 3.15.7 for new api.
View Lorry Controller Status