docs/devel/build-system.rst

12 The two general ways to perform a build are as follows:
44    firmware and tests.  The results are written as either Makefile
55 which a same-named Meson option exists; dashes in the command line are
98 functioning.  These are performed using a few more helper functions:
117    such checks are done at ``make`` time instead (see for example the
138 likewise, there are no options such as ``--meson`` or ``--sphinx-build``.
154 the dependencies are not present.
156 .. [#distlib] The scripts are created based on the package's metadata,
167 The required versions of the packages are stored in a configuration file
173 When dependencies are downloaded, instead, ``configure`` uses a "known
182 Python packages that are **mandatory** dependencies to build QEMU,
183 but are not available in all supported distros, are bundled with the
215 All executables are built by default, except for some ``contrib/``
216 binaries that are known to fail to build on some platforms (for example
217 32-bit or big-endian platforms).  Tests are also built by default,
223 ``meson.build`` files group the source files in rules that are
228   Various subsystems that are common to both tools and emulators have
231   are then turned into static libraries as follows::
241   the .o files are linked into all output binaries that need it.
253   once for each target being built.  Target-dependent files are included
272   of the ``target_arch`` and ``target_system_arch``, which are used respectively
282   There are two dictionaries for modules: ``modules`` is used for
284   target-dependent modules.  When modules are disabled the ``module``
285   source sets are added to ``system_ss`` and the ``target_modules``
286   source sets are added to ``specific_ss``.
288   Both dictionaries are nested.  One dictionary is created per
289   subdirectory, and these per-subdirectory dictionaries are added to
301   code, and the only two of general interest are ``util_ss`` and ``stub_ss``.
306   these and depend on other functions that are not fully implemented by
313 The following files concur in the definition of which files are linked
318   that are built into each QEMU system emulation targets. They merely contain
326   These files are processed together with ``configs/devices/*.mak`` and
328   device models.  They are described in :ref:`kconfig`
334   ``target/`` subdirectories that are compiled into each target.
339 These files rarely need changing unless you are adding a completely
380 Most of the libraries used by system-mode emulators are not available for
423 By the time Meson runs, Python dependencies are available in the virtual
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
475 The following key files are statically defined in the source tree, with
487   executables.  Build rules for various subdirectories are included in
511 The following files are generated at run-time in order to control the
573   features for each target.  enabled.  They are generated from
590   meson.build.  The rules are produced from Meson's JSON description of