mutter/clutter/clutter/clutter-config.h.in

#if !defined(__CLUTTER_H_INSIDE__) && !defined(CLUTTER_COMPILATION)
#error "Only <clutter/clutter.h> can be included directly."
#endif

#ifndef __CLUTTER_CONFIG_H__
#define __CLUTTER_CONFIG_H__

#include <glib.h>

G_BEGIN_DECLS

#mesondefine CLUTTER_HAS_WAYLAND_COMPOSITOR_SUPPORT
#mesondefine CLUTTER_WINDOWING_X11
#mesondefine CLUTTER_INPUT_X11
#mesondefine CLUTTER_WINDOWING_GLX
#mesondefine CLUTTER_WINDOWING_EGL
#mesondefine CLUTTER_INPUT_EVDEV
#mesondefine CLUTTER_INPUT_NULL

G_END_DECLS

#endif /* __CLUTTER_CONFIG_H__ */
build: Generate an instealled config header Clutter has some platform-specific API that is accessible only if the right backend has been compiled in. Third party applications that wish to be portable across backends might want to use defines and other pre-processor tricks to determine header inclusion and API usage. While Clutter has an internal set of symbols it can use, third party applications don't have the luxury of being able to access the config.h generated by Clutter's configure script. For this reason, Clutter should install a configuration header with a series of namespaced defines that can be picked up by applications and other third party code. 2011-01-19 14:33:27 +00:00			`#if !defined(__CLUTTER_H_INSIDE__) && !defined(CLUTTER_COMPILATION)`
			`#error "Only <clutter/clutter.h> can be included directly."`
			`#endif`

			`#ifndef __CLUTTER_CONFIG_H__`
			`#define __CLUTTER_CONFIG_H__`

			`#include <glib.h>`

			`G_BEGIN_DECLS`

clutter: Use #mesondefine Use #mesondefine instead of manual concatenation. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1179 2020-04-05 11:45:49 +02:00			`#mesondefine CLUTTER_HAS_WAYLAND_COMPOSITOR_SUPPORT`
			`#mesondefine CLUTTER_WINDOWING_X11`
			`#mesondefine CLUTTER_INPUT_X11`
			`#mesondefine CLUTTER_WINDOWING_GLX`
			`#mesondefine CLUTTER_WINDOWING_EGL`
			`#mesondefine CLUTTER_INPUT_EVDEV`
			`#mesondefine CLUTTER_INPUT_NULL`
build: Generate an instealled config header Clutter has some platform-specific API that is accessible only if the right backend has been compiled in. Third party applications that wish to be portable across backends might want to use defines and other pre-processor tricks to determine header inclusion and API usage. While Clutter has an internal set of symbols it can use, third party applications don't have the luxury of being able to access the config.h generated by Clutter's configure script. For this reason, Clutter should install a configuration header with a series of namespaced defines that can be picked up by applications and other third party code. 2011-01-19 14:33:27 +00:00
			`G_END_DECLS`

			`#endif /* __CLUTTER_CONFIG_H__ */`