The Meson Build System http://mesonbuild.com/

History

Eli Schwartz 398c4b2287 dependencies: allow get_variable to define multiple pkgconfig defines It was previously impossible to do this: ``` dep.get_pkgconfig_variable( 'foo', define_variable: ['prefix', '/usr', 'datadir', '/usr/share'], ) ``` since get_pkgconfig_variable mandated exactly two (if any) arguments. However, you could do this: ``` dep.get_variable( 'foo', pkgconfig_define: ['prefix', '/usr', 'datadir', '/usr/share'], ) ``` It would silently do the wrong thing, by defining "prefix" as `/usr=datadir=/usr/share`, which might not "matter" if only datadir was used in the "foo" variable as the unmodified value might be adequate. The actual intention of anyone writing such a meson.build is that they aren't sure whether the .pc file uses ${prefix} or ${datadir} (or which one gets used, might have changed between versions of that .pc file, even). A recent refactor made this into a hard error, which broke some projects that were doing this and inadvertently depending on some .pc file that only used the second variable. (This was "fine" since the result was essentially meaningful, and even resulted in behavior identical to the intended behavior if both projects were installed into the same prefix -- in which case there's nothing to remap.) Re-allow this. There are two ways we could re-allow this: - ignore it with a warning - add a new feature to allow actually doing this Since the use case which triggered this bug actually has a pretty good reason to want to do this, it makes sense to add the new feature. Fixes https://bugs.gentoo.org/916576 Fixes https://github.com/containers/bubblewrap/issues/609		1 year ago
..
extensions	Fix typos in docs	2 years ago
markdown	dependencies: allow get_variable to define multiple pkgconfig defines	1 year ago
refman	docs: refman: add vim syntax file generator	1 year ago
theme/extra	modules/wayland: Add unstable_wayland module	3 years ago
yaml	dependencies: allow get_variable to define multiple pkgconfig defines	1 year ago
.editorconfig	…
README.md	docs: mention additional python modules needed for building	2 years ago
genrefman.py	docs: Initial reference manual generator	3 years ago
genrelnotes.py	doc: Add date in release notes	2 years ago
jsonvalidator.py	docs: refman: Add `arg_flattening` support	3 years ago
meson.build	docs: mention additional python modules needed for building	2 years ago
meson_options.txt	docs: add option to skip building HTML docs	2 years ago
sitemap.txt	Whoopsie, forgot to create the release notes.	1 year ago

README.md

Meson Documentation

Build dependencies

Meson uses itself and hotdoc for generating documentation.

Minimum required version of hotdoc is 0.8.9.

Instructions on how to install hotdoc are here.

Our custom hotdoc extensions require:

Building the documentation

From the Meson repository root dir:

$ cd docs/
$ meson setup built_docs/
$ ninja -C built_docs/

Now you should be able to open the documentation locally

built_docs/Meson documentation-doc/html/index.html

Upload

Meson uses the git-upload hotdoc plugin which basically removes the html pages and replaces with the new content.

You can simply run:

$ ninja -C built_docs/ upload