Lines Matching full: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
124 The Initial Configuration
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
160    configuration directory, the result of merging it with :file:`prj.conf` is
165    configuration directory, the result of merging it with :file:`prj.conf` and
168 #. Otherwise, :file:`prj.conf` is used from the application configuration
171 Furthermore, applications can have SoC overlay configuration that is applied to
173 after the main project configuration has been applied and before any board overlay
174 configuration files have been applied.
176 All configuration files will be taken from the application's configuration
184 See :ref:`Application Configuration Directory <application-configuration-directory>`
185 on how the application configuration directory is defined.
188 application configuration, the value set in the application configuration takes
191 The merged configuration is saved to :file:`zephyr/.config` in the build
195 ``BOARD`` and application configuration files), it will be used in preference
196 to producing a new merged configuration. :file:`zephyr/.config` is also the
197 configuration that gets modified when making changes in the :ref:`interactive
198 configuration interfaces <menuconfig>`.
253 When making changes to the default configuration for a board, you might have to
347    symbol's direct dependencies in one of the :ref:`interactive configuration
356 One motivation for this configuration scheme is to avoid making fixed
357 ``BOARD``-specific settings configurable in the interactive configuration
358 interfaces. If all board configuration were done via :file:`<BOARD>_defconfig`,
362 Having fixed settings be user-configurable would clutter up the configuration
375 1. By setting one of the choice symbols to ``y`` in a configuration file.