Lines Matching refs:configuration

3 Setting Kconfig configuration values
26   up in the interactive configuration interfaces (hence *visible*), and can be
27   set in configuration files.
44   not shown in the interactive configuration interfaces, and users have no
61 Setting symbols in configuration files
64 Visible symbols can be configured by setting them in configuration files. The
65 initial configuration is produced by merging a :file:`*_defconfig` file for the
69 Assignments in configuration files use this syntax:
94    This is the format you will see in the merged configuration in
97    This style is accepted for historical reasons: Kconfig configuration files
114 Assignments in configuration files are only respected if the dependencies for
117 configuration interfaces <menuconfig>` (you can jump directly to a symbol with
127 The initial configuration for an application comes from merging configuration
130 1. A ``BOARD``-specific configuration file stored in
135 3. The application configuration
137 The application configuration can come from the sources below (each file is
139 configuration used for a particular build). By default, :file:`prj.conf` is
142 #. If ``CONF_FILE`` is set, the configuration file(s) specified in it are
143    merged and used as the application configuration. ``CONF_FILE`` can be set
152    Furthermore if ``CONF_FILE`` is set as single configuration file of the
159    configuration directory.
162    configuration directory, the result of merging it with :file:`prj.conf` is
167    configuration directory, the result of merging it with :file:`prj.conf` and
170 #. Otherwise, :file:`prj.conf` is used from the application configuration
173 All configuration files will be taken from the application's configuration
181 See :ref:`Application Configuration Directory <application-configuration-directory>`
182 on how the application configuration directory is defined.
185 application configuration, the value set in the application configuration takes
188 The merged configuration is saved to :file:`zephyr/.config` in the build
192 ``BOARD`` and application configuration files), it will be used in preference
193 to producing a new merged configuration. :file:`zephyr/.config` is also the
194 configuration that gets modified when making changes in the :ref:`interactive
195 configuration interfaces <menuconfig>`.
201 When making changes to the default configuration for a board, you might have to
269    symbol's direct dependencies in one of the :ref:`interactive configuration
278 One motivation for this configuration scheme is to avoid making fixed
279 ``BOARD``-specific settings configurable in the interactive configuration
280 interfaces. If all board configuration were done via :file:`<BOARD>_defconfig`,
284 Having fixed settings be user-configurable would clutter up the configuration
297 1. By setting one of the choice symbols to ``y`` in a configuration file.