gnome-shell/subprojects/extensions-tool/meson_options.txt

option('man',
  type: 'boolean',
  value: true,
  description: 'Generate man pages',
  yield: true,
)

option('bash_completion',
  type: 'feature',
  value: 'auto',
  description: 'Install bash completion support',
)

option('package_name',
  type: 'string',
  description: 'The gettext domain name when used as a subproject'
)
extensions-tool: Move to a subproject The gnome-extensions tool code is really independent from the rest of the code base, and could be used either as part of the gnome-shell build or as stand-alone project (for example for the extension-ci docker image). We can actually support both cases by moving the code to a subproject. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/877 2019-12-02 18:07:01 -05:00			`option('man',`
			`type: 'boolean',`
			`value: true,`
build: Yield 'man' option to extension-tool subproject Turns out meson has a build-in pattern of what we are doing, namely: Set a subproject option to a parent project option of the same name. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1072 2020-03-04 21:54:23 -05:00			`description: 'Generate man pages',`
			`yield: true,`
extensions-tool: Move to a subproject The gnome-extensions tool code is really independent from the rest of the code base, and could be used either as part of the gnome-shell build or as stand-alone project (for example for the extension-ci docker image). We can actually support both cases by moving the code to a subproject. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/877 2019-12-02 18:07:01 -05:00			`)`

build: Make bash-completion support optional Whether we install bash-completion support currently depends on whether the corresponding pkg-config dependency is found. Turning this into a feature option keeps that behavior by default, but also allows to explicitly enable or disable the support. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1072 2020-03-05 08:56:13 -05:00			`option('bash_completion',`
			`type: 'feature',`
			`value: 'auto',`
			`description: 'Install bash completion support',`
			`)`

extensions-tool: Move to a subproject The gnome-extensions tool code is really independent from the rest of the code base, and could be used either as part of the gnome-shell build or as stand-alone project (for example for the extension-ci docker image). We can actually support both cases by moving the code to a subproject. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/877 2019-12-02 18:07:01 -05:00			`option('package_name',`
			`type: 'string',`
build: Use fixed gettext domain for non-subproject extension-tool builds Clarify how the option is supposed to be used by - ignoring it for non-subproject builds - enforcing that it is set for subproject builds https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1072 2020-03-05 08:28:21 -05:00			`description: 'The gettext domain name when used as a subproject'`
extensions-tool: Move to a subproject The gnome-extensions tool code is really independent from the rest of the code base, and could be used either as part of the gnome-shell build or as stand-alone project (for example for the extension-ci docker image). We can actually support both cases by moving the code to a subproject. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/877 2019-12-02 18:07:01 -05:00			`)`