Lines Matching full:in

17 are included in QEMU's source code.  As a result, each QEMU executable
24 * new targets and boards can be added without knowing in detail the
37 originated in the Linux kernel, though it was heavily simplified and
38 the handling of dependencies is stricter in QEMU.
41 is instead specified in per-target files under the ``configs/``
44 QEMU; the default configuration that QEMU ships with should be okay in
50 Kconfig defines configurable components in files named ``hw/*/Kconfig``.
51 Note that configurable components are _not_ visible in C code as preprocessor
52 symbols; they are only visible in the Makefile.  Each configurable component
56 falsehood is written ``n``.  They are defined in a Kconfig
68 The ``config`` keyword introduces a new configuration element.  In the example
73 is written in the remainder of this section.  The ``&&``, ``||`` and
90   be used to force another symbol to true.  In the following example,
138 Configurable elements in QEMU fall under five broad groups.  Each group
139 declares its dependencies in different ways:
149   and are never visible in ``configs/*.mak`` files.  It's
152   They sometimes have ``select`` directives to bring in other required
190   devices in one go.  This is useful when a set of devices is likely to
192   no directive and are not used in the Makefile either; they only appear
201   that users might reasonably want to plug in to an i2c bus on any
203   to be wired up in a way that can't be done on the command line).
236   virtualization, in which case they also depend on the ``TCG`` symbol,
241   Boards are listed for convenience in the ``configs/*.mak``
252   Internal elements group code that is useful in several boards or
253   devices.  They are usually enabled with ``select`` and in turn select
254   other elements; they are never visible in ``configs/*.mak``
255   files, and often not even in the Makefile.
260 In addition to the Kconfig files under hw/, each target also includes
265 A file in ``configs/`` looks like the following example::
282 the default configuration by uncommenting lines in the first group,
283 or commenting out lines in the second group.
287 to ``n`` unless it is ``select``\ ed or explicitly switched on in the
288 ``.mak`` files.  In other words, ``default`` and ``imply`` directives
290 want to change some lines in the first group, for example like this::
295 and/or pick a subset of the devices in those device groups.  Without
300 fail, but should never abort.  Failures in ``make check`` with
301 ``--without-default-devices`` are considered bugs in the test code:
303 if a necessary device is not present in the build.  Such failures
307 for ``CONFIG_PCI_DEVICES`` and ``CONFIG_TEST_DEVICES``.  In the future,
314 In some special cases, a configurable element depends on host features
319 These symbols should be listed in ``Kconfig.host`` like this::
324 and also listed as follows in the top-level meson.build's host_kconfig