docs/devel/build-system.rst

29 Most of the actual build process uses Meson under the hood, therefore
45    fragments (``config-host.mak``) or a Meson machine file
46    (``config-meson.cross``)
51  - invoke Meson in the virtual environment, to perform the actual
55 which a same-named Meson option exists; dashes in the command line are
59 only be concerned with Meson, and therefore can skip the rest of this
82    replacement in Meson is ``find_program()``.
137 look for ``meson`` or ``sphinx-build`` binaries in the PATH;
138 likewise, there are no options such as ``--meson`` or ``--sphinx-build``.
139 This avoids a potential mismatch, where Meson and Sphinx binaries on the
184 QEMU sources.  The only one is currently Meson (outdated in Ubuntu
193 Stage 2: Meson
196 The Meson build system describes the build and install process for:
222 compilation as possible. Using the Meson "sourceset" functionality,
223 ``meson.build`` files group the source files in rules that are
354  - Add a Meson build option to meson_options.txt.
392 ``scripts/meson-buildoptions.sh`` file must be up-to-date; ``make
399 Meson has a special convention for invoking Python scripts: if their
402 interpreter that was used to invoke Meson.  This is the most common
403 and preferred way to invoke support scripts from Meson build files,
412 should be invoked through the ``python`` variable in meson.build. For
423 By the time Meson runs, Python dependencies are available in the virtual
425 places under ``pyvenv``.  One way to do so is as follows, using Meson's
439 The output of Meson is a ``build.ninja`` file, which is used with the
447 Tests, whether defined in ``meson.build`` or not, are also ran by the
449 are run with ``make bench``.  Meson test suites such as ``unit`` can be ran
450 with ``make check-unit``, and ``make check-tcg`` builds and runs "non-Meson"
453 If desired, it is also possible to use ``ninja`` and ``meson test``,
454 respectively to build emulators and run tests defined in meson.build.
484 ``*/meson.build``
485   The meson.build file in the root directory is the main entry point for the
486   Meson build system, and it coordinates the configuration and build of all
488   other meson.build files spread throughout the QEMU source tree.
521   and to a smaller extent ``meson.build``.
527 ``config-meson.cross``
529   A Meson "cross file" (or native file) used to communicate the paths to
554   that is run via ``sphinx-build``, ``meson`` etc. uses the same interpreter
557 Built by Meson:
565   generated by Meson using files under ``configs/devices`` as input.
569   generated by Meson using files under ``configs/targets`` as input.
574   the contents of the corresponding ``*.mak`` files using Meson's
586   Makefile is mostly a list of targets that Meson included in build.ninja.
590   meson.build.  The rules are produced from Meson's JSON description of
591   tests (obtained with "meson introspect --tests") through the script