dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gimp/meson_options.txt

67 lines
5.4 KiB
Meson
Raw Normal View History

Meson port.
2017-11-01 21:27:13 +08:00
# Build properties
meson: fix relocatable-bundle feature and mypaint-brushes dependency. It must not be a boolean but a `feature` option, with `auto` by default. `auto` value mean enabled for macOS and Win32, and disabled for other cases. This default logics disappeared in the meson build. Also the mypaint-brushes package is a mandatory dependency, which must always be checked. Absence is fatale. Finally properly set the MYPAINT_BRUSHES_DIR macro depending on the proper relocatable case.
2019-09-21 19:32:13 +08:00
option('ansi', type: 'boolean', value: false, description: 'Turn on strict ansi')
option('enable-console-bin',type: 'boolean', value: true, description: 'Build a console-only binary which does not link GTK+')
option('win32-debug-console',type:'boolean', value: true, description: 'Open a console when starting the program')
option('enable-default-bin',type: 'boolean', value: true, description: 'Build default Gtk+ binary')
option('enable-multiproc', type: 'boolean', value: true, description: 'Support for multiple processors')
option('profiling', type: 'boolean', value: false, description: 'Enable profiling')
option('windows-installer', type: 'boolean', value: false, description: 'Generate files needed for the Windows installer')
meson: change option relocatable-bundle = yes|no|platform-default As discussed in patch !208. Now that the feature is implemented as a meson combo, let's have (hopefully) clearer values than enabled|disabled|auto.
2020-03-18 01:48:54 +08:00
option('relocatable-bundle', type: 'combo', value: 'platform-default',
description: 'build with resources considered bundled under the same prefix',
choices: [ 'yes', 'no', 'platform-default' ])
meson: fix relocatable-bundle feature and mypaint-brushes dependency. It must not be a boolean but a `feature` option, with `auto` by default. `auto` value mean enabled for macOS and Win32, and disabled for other cases. This default logics disappeared in the meson build. Also the mypaint-brushes package is a mandatory dependency, which must always be checked. Absence is fatale. Finally properly set the MYPAINT_BRUSHES_DIR macro depending on the proper relocatable case.
2019-09-21 19:32:13 +08:00
option('shmem-type', type: 'combo', value: 'auto', description: 'Shared memory transport type',
choices: [ 'none', 'sysv', 'posix', 'win32', 'auto' ])
meson: new build id and revision also in meson configuration.
2019-11-30 22:27:30 +08:00
option('build-id', type: 'string', value: 'unknown', description: 'Unique string used to define your build')
meson, data: create/install gimp-release file with meson too.
2020-02-14 07:58:22 +08:00
option('revision', type: 'integer', value: 0, description: 'Revision increment for a package')
meson: -Dcheck-update option as a yes|no|platform-default combo. Similar to the previous commit for the meson build system, the 'check-update' option is not a boolean anymore, but has now 3 values.
2021-08-26 07:22:32 +08:00
option('check-update', type: 'combo', value: 'platform-default',
description: 'GIMP will look up new version availability on startup',
choices: [ 'yes', 'no', 'platform-default' ])
meson: same option for meson -Dcheck-update=false as previous commit. Separate commit for easy cherry-picking.
2020-02-07 04:20:17 +08:00
Meson port.
2017-11-01 21:27:13 +08:00
option('bug-report-url', type: 'string', value: '', description: 'URL used by the debug dialog to report bugs')
option('gimpdir', type: 'string', value: '', description: 'Change default gimpdir from ~/.config/GIMP/2.9 to ~/.config/DIR/2.9 (if relative), or to DIR (if absolute)')
option('icc-directory', type: 'string', value: '', description: 'Path to default color profiles for this system')
option('directx-sdk-dir', type: 'string', value: '', description: 'Prefix where the DirectX SDK is installed(optional)')
option('with-sendmail', type: 'string', value: '', description: 'Use Sendmail instead of Xdg-email')
option('win32-32bits-dll-folder', type: 'string', value: '32/bin', description: 'alternative folder with 32-bit versions of DLL libraries on Windows')
option('libunwind', type: 'boolean', value: true, description: 'Build with libunwind for backtrace')
option('libbacktrace', type: 'boolean', value: true, description: 'Build with libbacktrace support')
# Features
option('aa', type: 'feature', value: 'auto', description: 'AA plugin')
option('alsa', type: 'feature', value: 'auto', description: 'Alsa support in midi input controller')
option('appdata-test', type: 'feature', value: 'auto', description: 'Validate the appdata file')
option('cairo-pdf', type: 'feature', value: 'auto', description: 'Cairo-pdf support')
option('ghostscript', type: 'feature', value: 'auto', description: 'Ghostscript support')
option('gudev', type: 'feature', value: 'auto', description: 'Gudev support')
option('heif', type: 'feature', value: 'auto', description: 'HEIF support')
option('jpeg2000', type: 'feature', value: 'auto', description: 'Jpeg-2000 support')
Add JPEG XL plug-in
2021-08-26 20:24:21 +08:00
option('jpeg-xl', type: 'feature', value: 'auto', description: 'JPEG XL support')
Meson port.
2017-11-01 21:27:13 +08:00
option('mng', type: 'feature', value: 'auto', description: 'Mng support')
option('openexr', type: 'feature', value: 'auto', description: 'Openexr support')
Try to reenable Print plugin on Windows. Let's see if the CI passes.
2020-07-06 17:03:21 +08:00
option('print', type: 'boolean', value: true, description: 'Print support')
configure, meson, plug-ins: unmaintain WebkitGTK-depending plug-ins. This is an official way to declare these plug-ins as now unmaintained/deprecated. Relevant plug-ins are: 1) help-browser (Displaying the docs): nowadays every desktop machine has a browser. Let's just use whatever is the person's default browser. 2) web-page (Web screenshot): it looks to me like every browser has this feature by default now (I use it all the time in Firefox to get a full-page screenshot, never in GIMP), even on mobile, I am told. It's nice to have it in GIMP too, but not like absolutely necessary. On the other hand: 1. It's a hell to build, with a lot of issues. We have regular issues on our Flatpak-s. We don't manage to build it on our CI (only locally apparently). Also it takes a crazy amount of time (like 90% of CI build-time would be webkit). 2. From what I gather, new versions don't work on Windows anymore. Even MSYS2 seems to have dropped the ball and don't try anymore. Basically we would have a feature disparity from GIMP 3.0 (most platform but Windows). We don't know when it will be resolved (if ever) as it's been like this for years. Now why we are keeping the code around instead of just removing everything is that the topic tree in the help browser is useful and comfortable to use. Ideally we should get some equivalent to help browsing the help efficiently in the web docs as well (so basically menus, web search and alike?). So I am told to keep the code around at least for now to see if we can figure something out or improve the situation. Except for this point, we can consider the WebkitGTK plug-ins as deprecated from GIMP 3.0 on.
2021-12-23 01:47:30 +08:00
option('webkit-unmaintained',type: 'boolean', value: false, description: 'Help browser and webpage plugins (unmaintained)')
Meson port.
2017-11-01 21:27:13 +08:00
option('webp', type: 'feature', value: 'auto', description: 'Webp support')
option('wmf', type: 'feature', value: 'auto', description: 'Wmf support')
option('xcursor', type: 'feature', value: 'auto', description: 'Xcursor support')
option('xpm', type: 'feature', value: 'auto', description: 'XPM support')
meson: Allow running tests headless This commit makes sure we can properly run the tests in a headless environment, i.e. they don't mess with the user's X display or their session bus. The latter is also needed for parallel tests as they fail to simultaneously own the same name on the session bus. Replaced the "xvfb-run" meson option with the "headless" option, which is more intuitive (and also more correct, since we now also require `dbus-run-session` to run the tests, not only `xvfb-run`). Finally, note that we need a version of `xvfb-run` that supports the `-d` (`--auto-display`) option. The problem with `--auto-servernum` which is also regularly used, is that it doesn't shut down cleanly, returning a non-zero exit code, wich makes the test fail. Fixes https://gitlab.gnome.org/GNOME/gimp/-/issues/5078
2020-05-14 23:51:55 +08:00
option('headless-tests', type: 'feature', value: 'auto', description: 'Use xvfb-run/dbus-run-session for UI-dependent automatic tests')
Meson port.
2017-11-01 21:27:13 +08:00
meson: make gir buildable yocto/oe is capable of building gobject introspection despite cross-compiling. add an option to enable gir build even if cross-compiling Signed-off-by: Markus Volk <f_l_k@t-online.de> Reviewer note (Jehan): this whole stuff is a mess. Actually I'd like to simply get rid of the whole no-gir-when-cross-compiling logics but I still can't figure out how to cross-build generically with GIR. Yet since some manage it with yocto, let's unblock them. See #7208.
2021-09-01 22:44:13 +08:00
option('can-crosscompile-gir', type: 'boolean', value: false, description: 'GIR is buildable even if crosscompiling')
configure, meson, devel-docs: make gi-docgen into an auto option. Also called "feature" option in meson, so that by default it depends on auto-detection of the gi-docgen hence won't break the configuration when the tool is missing (the feature is simply disabled). Also move the program check into the root meson file, which is anyway much better to have a better visibility of features, otherwise we'd end up just having tests everywhere in any possible random directory of the repo. Finally add a line in the summary of the configuration step, displaying the docs generation being enabled or disabled.
2021-12-29 07:55:17 +08:00
option('gi-docgen', type: 'feature', value: 'auto', description: 'Build developer documentation (uses gi-docgen)')
devel-docs, meson: g-ir-doc option to generate introspected API docs. Similar to the --enable-g-ir-doc option I just added on autotools. Also separate this option from gtk-doc as it is unrelated (not everything under devel-docs is related to gtk-doc!).
2021-01-29 23:51:47 +08:00
option('g-ir-doc', type: 'boolean', value: false, description: 'Build developer documentation for introspected API')
Meson port.
2017-11-01 21:27:13 +08:00
option('linux-input', type: 'feature', value: 'auto', description: 'Linux input event controller module')
option('vec-icons', type: 'boolean', value: true, description: 'Use vector icons rather than raster ones')
meson, autotools, CI: simplify plug-in binding build options. For Python, Lua and Javascript, make the option boolean (with 'yes' being the default). No need of a warning when not installing the plug-ins as this would have been disabled explicitly anyway. When installing the plug-ins, only make interpreter checks as precautionnary verifications which don't actually change anything (except outputting some warnings if interpreters are not found). Basically for these 3 bindings, the interpreters are only runtime dependencies anyway. So it doesn't matter if they are not available at build time. In particular, we get rid of the 'force' option. Vala rules do not change as the vala compiler is indeed needed at build time and current checks work correctly. I just add a "Vala plug-ins" line in the summary message of the meson configuration, as it was missing.
2020-10-13 04:02:46 +08:00
option('vala-plugins', type: 'feature', value: 'auto', description: 'Build VAPI and Vala plugins')
option('javascript', type: 'boolean', value: true, description: 'Install Javascript plug-ins')
option('lua', type: 'boolean', value: true, description: 'Install Lua plug-ins')
option('python', type: 'boolean', value: true, description: 'Install Python 3 plug-ins')