AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
420c4e1f16
gtk2/meson_options.txt

58 lines
2.7 KiB
Meson
Raw Normal View History

build: Coalesce print backends options into one Instead of having separate options for each print backend, we can use the same approach as the input method modules: a single option, with a comma-separated list of print backends.
2018-02-14 13:55:32 +00:00
# GDK backends
build: Rename GDK backend options Drop the 'enable-' prefix, and always enable all platform-specific backends. We can disable them depending on the platform. This way, the documentation printed by `meson configure` remains accurate.
2018-02-14 14:04:04 +00:00
option('x11-backend', type: 'boolean', value: true,
build: Make the default setting work on non-Linux Unix-like systems All of the four platform-dependent backends are enabled by default. It is usually a good default because it requires users to explicitly choose backends they want to use. Rules in meson.build also automatically disable unavailable backends for macOS, Windows, Linux, so users on these 3 major platforms don't have to manually disable things when running meson commands. However, meson.build doesn't do the same thing for other Unix-like systems, which is acceptable but not ideal. To make it easier to build GTK+ on these systems, the Linux case, which enables X11 and Wayland and disables Win32 and Quartz, is made the default for all operating systems that are not Windows or macOS. This commit also changes most 'host_machine.system()' calls to os_* variables, which are easier to read and less likely to be used wrongly.
2018-04-22 12:47:32 +00:00
description : 'Enable the X11 gdk backend (only when building on Unix)')
build: Rename GDK backend options Drop the 'enable-' prefix, and always enable all platform-specific backends. We can disable them depending on the platform. This way, the documentation printed by `meson configure` remains accurate.
2018-02-14 14:04:04 +00:00
option('wayland-backend', type: 'boolean', value: true,
build: Make the default setting work on non-Linux Unix-like systems All of the four platform-dependent backends are enabled by default. It is usually a good default because it requires users to explicitly choose backends they want to use. Rules in meson.build also automatically disable unavailable backends for macOS, Windows, Linux, so users on these 3 major platforms don't have to manually disable things when running meson commands. However, meson.build doesn't do the same thing for other Unix-like systems, which is acceptable but not ideal. To make it easier to build GTK+ on these systems, the Linux case, which enables X11 and Wayland and disables Win32 and Quartz, is made the default for all operating systems that are not Windows or macOS. This commit also changes most 'host_machine.system()' calls to os_* variables, which are easier to read and less likely to be used wrongly.
2018-04-22 12:47:32 +00:00
description : 'Enable the wayland gdk backend (only when building on Unix except for macOS)')
build: Rename GDK backend options Drop the 'enable-' prefix, and always enable all platform-specific backends. We can disable them depending on the platform. This way, the documentation printed by `meson configure` remains accurate.
2018-02-14 14:04:04 +00:00
option('broadway-backend', type: 'boolean', value: false,
meson: gdk: add Mir backend bits Completely untested, might not even build.
2017-03-20 11:44:04 +00:00
description : 'Enable the broadway (HTML5) gdk backend')
build: Rename GDK backend options Drop the 'enable-' prefix, and always enable all platform-specific backends. We can disable them depending on the platform. This way, the documentation printed by `meson configure` remains accurate.
2018-02-14 14:04:04 +00:00
option('win32-backend', type: 'boolean', value: true,
description : 'Enable the Windows gdk backend (only when building on Windows)')
option('quartz-backend', type: 'boolean', value: true,
description : 'Enable the macOS gdk backend (only when building on macOS)')
macos: prototype new GDK backend for macOS This is fairly substantial rewrite of the GDK backend for quartz and renamed to macOS to allow for a greenfield implementation. Many things have come across from the quartz implementation fairly intact such as the eventloop integration design and discovery of event windows from the NSEvent. However much has been changed to fit in with the new GDK design and how removal of child GdkWindow have been completely eliminated. Furthermore, the new GdkPopup allows for regular NSWindow to be used to provide popovers unlike the previous implementation. The object design more closely follows the ideal for a GDK backend. Views have been broken out into subclasses so that we can support multiple GSK renderer paths such as GL and Cairo (and Metal in the future). However mixed mode GL and Cairo will not be supported. Currently only the Cairo renderer has been implemented. A new frame clock implementation using CVDisplayLink provides more accurate information about when to draw drawing the next frame. Some testing will need to be done here to understand the power implications of this. This implementation has also gained edge snapping for CSD windows. Some work was also done to ensure that CSD windows have opaque regions registered with the display server. ** This is still very much a work-in-progress ** Some outstanding work that needs to be done: - Finish a GL context for macOS and alternate NSView for GL rendering (possibly using speciailized CALayer for OpenGL). - Input rework to ensure that we don't loose remapping of keys that was dropped from GDK during GTK 4 development. - Make sure input methods continue to work. - Drag-n-Drop is still very much a work in progress - High resolution input scrolling needs various work in GDK to land first before we can plumb that to NSEvent. - gtk/ has a number of things based on GDK_WINDOWING_QUARTZ that need to be updated to use the macOS backend. But this is good enough to start playing with and breaking things which is what I'd like to see.
2020-04-23 23:36:46 +00:00
option('macos-backend', type: 'boolean', value: true,
description : 'Enable the macOS gdk backend (only when building on macOS)')
build: Coalesce print backends options into one Instead of having separate options for each print backend, we can use the same approach as the input method modules: a single option, with a comma-separated list of print backends.
2018-02-14 13:55:32 +00:00
mediafile: Turn into an extension point This way, we can support external libraries providing implementations of GtkMediaFile. We also add a media backend called 'nomedia' that can be enabled to not compile any support for GtkMediaFile. This is useful when people want to statically compile GTK into an application that does not use media. For now, this option is the default. We also support a new environment variable GTK_MEDIA that allows selecting the implementation to use. GTK_MEDIA=help can be used to get info about the available implementations.
2018-03-01 20:46:16 +00:00
# Media backends
build: Make GStreamer backend the default Instead of compiling without media backend by default, we now use the GStreamer backend. This means that CI now requires gstreamer support.
2018-03-04 14:03:26 +00:00
option('media', type: 'string', value: 'gstreamer',
mediafile: Turn into an extension point This way, we can support external libraries providing implementations of GtkMediaFile. We also add a media backend called 'nomedia' that can be enabled to not compile any support for GtkMediaFile. This is useful when people want to statically compile GTK into an application that does not use media. For now, this option is the default. We also support a new environment variable GTK_MEDIA that allows selecting the implementation to use. GTK_MEDIA=help can be used to get info about the available implementations.
2018-03-01 20:46:16 +00:00
description : 'Build the specified media engines (comma-separated list, "all", or "none")')
build: Coalesce print backends options into one Instead of having separate options for each print backend, we can use the same approach as the input method modules: a single option, with a comma-separated list of print backends.
2018-02-14 13:55:32 +00:00
# Optional dependencies
build: Rename last 'enable' options Drop the 'enable-' prefix to conform to the best practices for naming configuration options in Meson.
2018-02-14 14:07:22 +00:00
option('vulkan', type: 'combo', choices : ['yes', 'no', 'auto'], value : 'auto',
meson: gdk: add Mir backend bits Completely untested, might not even build.
2017-03-20 11:44:04 +00:00
description : 'Enable support for the Vulkan graphics API')
build: Rename last 'enable' options Drop the 'enable-' prefix to conform to the best practices for naming configuration options in Meson.
2018-02-14 14:07:22 +00:00
option('xinerama', type: 'combo', choices : ['yes', 'no', 'auto'], value : 'auto',
meson: check for xinerama
2017-03-24 11:34:49 +00:00
description : 'Enable support for the Xinerama extension')
build: Rename last 'enable' options Drop the 'enable-' prefix to conform to the best practices for naming configuration options in Meson.
2018-02-14 14:07:22 +00:00
option('cloudproviders', type: 'boolean', value: false,
build: Coalesce print backends options into one Instead of having separate options for each print backend, we can use the same approach as the input method modules: a single option, with a comma-separated list of print backends.
2018-02-14 13:55:32 +00:00
description : 'Enable the cloudproviders support')
Rename the profiler option We don't support any profilers other than sysprof, so name the option accordingly. While we are at it, change it to a meson feature option, so -Dprofiler=true becomes -Dsysprof=enabled
2020-08-21 22:51:48 +00:00
option('sysprof',
type: 'feature',
value: 'disabled',
description : 'include tracing support for sysprof')
gtksearchengine: Add tracker3 search engine Make this dependency optional at build time, and prefer it over the old tracker <= 2.x implementation.
2020-05-16 22:04:56 +00:00
option('tracker3', type: 'boolean', value: false,
description : 'Enable Tracker3 filechooser search')
build: Coalesce print backends options into one Instead of having separate options for each print backend, we can use the same approach as the input method modules: a single option, with a comma-separated list of print backends.
2018-02-14 13:55:32 +00:00
# Print backends
Don't mention papi in options docs The papi print backend has been removed.
2018-02-24 06:02:17 +00:00
option('print-backends', type : 'string', value : 'cups,file',
build: Coalesce print backends options into one Instead of having separate options for each print backend, we can use the same approach as the input method modules: a single option, with a comma-separated list of print backends.
2018-02-14 13:55:32 +00:00
description : 'Build the specified print backends (comma-separated list, "all", or "none")')
option('colord', type: 'combo', choices : ['yes', 'no', 'auto'], value : 'auto',
description : 'Build colord support for the CUPS printing backend')
# Documentation and introspection
meson: Rename documentation option to gtk_doc This name is what most of the stack is using. Lets follow along, even though it is (imo) uglier.
2019-07-01 16:57:16 +00:00
option('gtk_doc', type: 'boolean', value: 'false',
build: Generate the API references (WIP) Still a work in progress.
2017-04-19 10:35:45 +00:00
description : 'Build API reference and tools documentation')
Rename enable-documentation and enable-man-pages options You can now disable the documentation build with -Ddocumentation=false and -Dman-pages=false.
2017-09-06 13:43:24 +00:00
option('man-pages', type: 'boolean', value: 'false',
meson: Generate man pages for the installed tools
2017-05-05 10:34:05 +00:00
description : 'Build man pages for installed tools')
Rename and document the enable-gir option You can disable introspection now with -Dintrospection=false.
2017-09-06 13:27:59 +00:00
option('introspection', type: 'boolean', value: 'true',
build: Add option to enable/disable GIR generation And drop the unnecessary is_cross_build() check: it's entirely possible to generate introspection data when cross-compiling.
2017-09-02 11:00:05 +00:00
description : 'Build introspection data (requires gobject-introspection)')
build: Coalesce print backends options into one Instead of having separate options for each print backend, we can use the same approach as the input method modules: a single option, with a comma-separated list of print backends.
2018-02-14 13:55:32 +00:00
# Demos and binaries
Allow building without tests and demos This is meant to cut down build time in flatpak and similar situations. Since it produces technically incomplete builds, we list these options in the status output at the end of the meson run.
2017-09-06 12:33:18 +00:00
option('demos', type: 'boolean', value: 'true',
Add an option for building examples Examples are not like demos; the latter are installed, and provide a Flatpak manifest for CI pipelines and GNOME Builder. We should not be using a single configure time option to gate building both.
2018-03-27 12:15:21 +00:00
description : 'Build demo programs')
option('build-examples', type: 'boolean', value: 'true',
description : 'Build examples')
Allow building without tests and demos This is meant to cut down build time in flatpak and similar situations. Since it produces technically incomplete builds, we list these options in the status output at the end of the meson run.
2017-09-06 12:33:18 +00:00
option('build-tests', type: 'boolean', value: 'true',
description : 'Build tests')
Add an install-tests option Use this to enable or disable installed tests.
2017-10-10 04:14:48 +00:00
option('install-tests', type: 'boolean', value: 'false',
description : 'Install tests')
Reference in New Issue Copy Permalink