7 Commits

Author	SHA1	Message	Date
Emmanuele Bassi	def700739d	Use a single compilation symbol ... We use a compilation symbol in our build to allow the inclusion of specific headers while building GTK, to avoid the need to include only the global header. Each namespace has its own compilation symbol because we used to have different libraries, and strict symbol visibility between libraries; now that we have a single library, and we can use private symbols across namespaces while building GTK, we should have a single compilation symbol, and simplify the build rules.	2019-11-27 13:33:43 +00:00
Andy Holmes	907a86fd93	Correct Gdk backend import paths and related gtk-doc ... Correct the paths in the include guard warnings and use the `@Include` directive for the Gdk backends.	2019-11-18 00:31:38 -08:00
Matthias Clasen	ca81028901	Add GDK_AVAILABLE_IN_ALL annotations in gdk ... This is in preparation to modernizing our handing of exported symbols.	2013-05-05 15:38:46 -04:00
Matthias Clasen	5adecf183b	Move single-include guards inside include guards ... gcc has optimizations for include guards that only work if they are outermost in the the header. https://bugzilla.gnome.org/show_bug.cgi?id=689810	2012-12-28 09:57:56 -05:00
Javier Jardón	9d0febc9a6	Change FSF Address	2012-02-27 17:06:11 +00:00
Kristian Rietveld	0d8eeb924e	quartz: _gdk_quartz_display -> gdk_quartz_display	2010-12-23 14:17:42 +01:00
Kristian Rietveld	caa9794af8	quartz: Clean up header files, use same arrangement as X11 backend	2010-12-23 14:17:41 +01:00