Lines Matching refs:Meson

29 Most of the actual build process uses Meson under the hood, therefore
45    fragments (``config-host.mak``) or a Meson machine file
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()``.
139 This avoids a potential mismatch, where Meson and Sphinx binaries on the
188 QEMU sources.  The only one is currently Meson (outdated in Ubuntu
197 Stage 2: Meson
200 The Meson build system describes the build and install process for:
226 compilation as possible. Using the Meson "sourceset" functionality,
358  - Add a Meson build option to meson_options.txt.
403 Meson has a special convention for invoking Python scripts: if their
406 interpreter that was used to invoke Meson.  This is the most common
407 and preferred way to invoke support scripts from Meson build files,
427 By the time Meson runs, Python dependencies are available in the virtual
429 places under ``pyvenv``.  One way to do so is as follows, using Meson's
443 The output of Meson is a ``build.ninja`` file, which is used with the
453 are run with ``make bench``.  Meson test suites such as ``unit`` can be ran
454 with ``make check-unit``, and ``make check-tcg`` builds and runs "non-Meson"
490   Meson build system, and it coordinates the configuration and build of all
534   A Meson "cross file" (or native file) used to communicate the paths to
562 Built by Meson:
570   generated by Meson using files under ``configs/devices`` as input.
574   generated by Meson using files under ``configs/targets`` as input.
579   the contents of the corresponding ``*.mak`` files using Meson's
591   Makefile is mostly a list of targets that Meson included in build.ninja.
595   meson.build.  The rules are produced from Meson's JSON description of