Lines Matching +full:check +full:- +full:common +full:- +full:files
11 <kconfig-search>`.
15 Before making changes to Kconfig files, it's a good idea to also go through
25 - A visible symbol is a symbol defined with a prompt. Visible symbols show
27 set in configuration files.
31 .. code-block:: kconfig
39 .. code-block:: none
43 - An *invisible* symbol is a symbol without a prompt. Invisible symbols are
50 .. code-block:: kconfig
61 Setting symbols in configuration files
64 Visible symbols can be configured by setting them in configuration files. The
67 :ref:`initial-conf` below for more details.
69 Assignments in configuration files use this syntax:
71 .. code-block:: cfg
81 .. code-block:: cfg
90 .. code-block:: cfg
97 This style is accepted for historical reasons: Kconfig configuration files
99 ``n``-valued symbols correspond to unset variables simplifies tests in Make.
103 .. code-block:: cfg
110 .. code-block:: cfg
114 Assignments in configuration files are only respected if the dependencies for
119 <kconfig-search>`.
122 .. _initial-conf:
130 1. A ``BOARD``-specific configuration file stored in
148 2. By passing ``-DCONF_FILE=<conf file(s)>``, either directly or via ``west``
156 :file:`boards/<BOARD>_<build>.conf` is used - note that this feature is
157 deprecated, :ref:`application-file-suffixes` should be used instead.
174 configuration files have been applied.
176 All configuration files will be taken from the application's configuration
177 directory except for files with an absolute path that are given with the
181 variable like this ``\${ZEPHYR_<module>_MODULE_DIR}/<path-to>/<file>``
184 See :ref:`Application Configuration Directory <application-configuration-directory>`
194 As long as :file:`zephyr/.config` exists and is up-to-date (is newer than any
195 ``BOARD`` and application configuration files), it will be used in preference
208 but do not want to rely directly on the common symbol. For example, you might
213 For example, consider the common ``FOO_STRING`` setting where a subsystem wants
218 .. code-block:: kconfig
225 string "Sub-foo"
236 .. code-block:: kconfig
247 Can be changed through *.defconfig files.
260 Assignments in :file:`.config` files have no effect on invisible symbols,
267 .. code-block:: kconfig
275 .. code-block:: kconfig
291 ``default`` values in :file:`Kconfig.defconfig` files have priority over
293 is implemented by including the :file:`Kconfig.defconfig` files first. Kconfig
297 Note that conditions from surrounding top-level ``if``\ s are propagated to
304 ---------------------------
316 .. code-block:: none
332 .. code-block:: kconfig
346 When making changes to :file:`Kconfig.defconfig` files, always check the
353 Motivation for Kconfig.defconfig files
354 --------------------------------------
357 ``BOARD``-specific settings configurable in the interactive configuration
362 Having fixed settings be user-configurable would clutter up the configuration
366 When dealing with fixed board-specific settings, also consider whether they
367 should be handled via :ref:`devicetree <dt-guide>` instead.
371 -------------------
393 .. code-block:: kconfig
410 .. code-block:: kconfig
425 files.