Lines Matching full:file
65 initial configuration is produced by merging a :file:`*_defconfig` file for the
66 board with application settings, usually from :file:`prj.conf`. See
95 saved to :file:`zephyr/.config` in the build directory.
130 1. A ``BOARD``-specific configuration file stored in
131 :file:`boards/<VENDOR>/<BOARD>/<BOARD>_defconfig`
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
146 1. In :file:`CMakeLists.txt`, before calling ``find_package(Zephyr)``
148 2. By passing ``-DCONF_FILE=<conf file(s)>``, either directly or via ``west``
152 Furthermore if ``CONF_FILE`` is set as single configuration file of the
153 form :file:`prj_<build>.conf` and if file
154 :file:`boards/<BOARD>_<build>.conf` exists in same folder as file
155 :file:`prj_<build>.conf`, the result of merging :file:`prj_<build>.conf` and
156 :file:`boards/<BOARD>_<build>.conf` is used - note that this feature is
157 deprecated, :ref:`application-file-suffixes` should be used instead.
159 #. Otherwise, if :file:`boards/<BOARD>.conf` exists in the application
160 configuration directory, the result of merging it with :file:`prj.conf` is
164 :file:`boards/<BOARD>_<revision>.conf` exists in the application
165 configuration directory, the result of merging it with :file:`prj.conf` and
166 :file:`boards/<BOARD>.conf` is used.
168 #. Otherwise, :file:`prj.conf` is used from the application configuration
172 it, the file :file:`socs/<SOC>_<BOARD_QUALIFIERS>.conf` will be applied if it exists,
180 a file in a Zephyr module can be referred by escaping the Zephyr module dir
181 variable like this ``\${ZEPHYR_<module>_MODULE_DIR}/<path-to>/<file>``
182 when setting any of said variables in the application's :file:`CMakeLists.txt`.
187 If a symbol is assigned both in :file:`<BOARD>_defconfig` and in the
191 The merged configuration is saved to :file:`zephyr/.config` in the build
194 As long as :file:`zephyr/.config` exists and is up-to-date (is newer than any
196 to producing a new merged configuration. :file:`zephyr/.config` is also the
234 :file:`defconfig` file.
255 :file:`boards/<VENDOR>/<BOARD>/Kconfig.defconfig`, which is a regular
256 :file:`Kconfig` file.
260 Assignments in :file:`.config` files have no effect on invisible symbols,
263 Assigning values in :file:`Kconfig.defconfig` relies on defining a Kconfig
273 :file:`Kconfig.defconfig`:
291 ``default`` values in :file:`Kconfig.defconfig` files have priority over
293 is implemented by including the :file:`Kconfig.defconfig` files first. Kconfig
346 When making changes to :file:`Kconfig.defconfig` files, always check the
358 interfaces. If all board configuration were done via :file:`<BOARD>_defconfig`,
360 :file:`<BOARD>_defconfig` have no effect on invisible symbols.
375 1. By setting one of the choice symbols to ``y`` in a configuration file.
382 selection from a board :file:`defconfig` file to be overridden from an
383 application :file:`prj.conf` file.
385 2. By changing the ``default`` of the choice in :file:`Kconfig.defconfig`.
408 following definition to :file:`Kconfig.defconfig`:
416 The :file:`Kconfig.defconfig` method should be used when the dependencies of
428 (at the top of the file) goes over how symbol values are calculated in detail.