Home
last modified time | relevance | path

Searched refs:CONF_FILE (Results 1 – 15 of 15) sorted by relevance

/Zephyr-latest/cmake/modules/
Dconfiguration_files.cmake13 # - CONF_FILE: List of Kconfig fragments
38 zephyr_get(CONF_FILE SYSBUILD LOCAL)
39 if(NOT DEFINED CONF_FILE)
40 …zephyr_file(CONF_FILES ${APPLICATION_CONFIG_DIR} KCONF CONF_FILE NAMES "prj.conf" SUFFIX ${FILE_SU…
41 …zephyr_file(CONF_FILES ${APPLICATION_CONFIG_DIR}/socs KCONF CONF_FILE QUALIFIERS SUFFIX ${FILE_SUF…
42 zephyr_file(CONF_FILES ${APPLICATION_CONFIG_DIR}/boards KCONF CONF_FILE SUFFIX ${FILE_SUFFIX})
44 string(CONFIGURE "${CONF_FILE}" CONF_FILE_EXPANDED)
48 get_filename_component(CONF_FILE_NAME ${CONF_FILE} NAME)
56 set(CONF_FILE ${CONF_FILE} CACHE STRING "If desired, you can build the application using\ variable
59 Multiple files may be listed, e.g. CONF_FILE=\"prj1.conf;prj2.conf\" \
[all …]
Dkconfig.cmake74 if(CONF_FILE)
75 string(CONFIGURE "${CONF_FILE}" CONF_FILE_EXPANDED)
361 # can use relative paths in CONF_FILE, e.g. CONF_FILE=nrf5.conf
/Zephyr-latest/share/sysbuild/cmake/modules/
Dsysbuild_kconfig.cmake92 set(CONF_FILE ${SB_CONF_FILE}) variable
117 set(CONF_FILE) variable
/Zephyr-latest/samples/subsys/fs/format/
DREADME.rst25 ``CONF_FILE=prj_ram.conf``.
/Zephyr-latest/tests/bluetooth/tester/
DREADME38 CONF_FILE=qemu.conf. After this qemu can be started through the "run"
/Zephyr-latest/doc/develop/application/
Dindex.rst395 The variables :makevar:`BOARD`, :makevar:`CONF_FILE`, and
415 * :makevar:`CONF_FILE`: Indicates the name of one or more Kconfig configuration
424 can be useful in order to leave :makevar:`CONF_FILE` at its default value,
497 the usual :file:`prj.conf`, add lines setting the :makevar:`CONF_FILE`
501 avoid setting :makevar:`CONF_FILE` in a single place. For example:
505 set(CONF_FILE "fragment_file1.conf")
506 list(APPEND CONF_FILE "fragment_file2.conf")
526 configuration options, refer to the :makevar:`CONF_FILE` description above.
617 described earlier, for example ``CONF_FILE``, ``EXTRA_CONF_FILE``,
838 specified in an alternate :file:`.conf` file using the :code:`CONF_FILE`
[all …]
/Zephyr-latest/doc/build/kconfig/
Dsetting.rst142 #. 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
171 ``CONF_FILE``, ``EXTRA_CONF_FILE``, ``DTC_OVERLAY_FILE``, and
/Zephyr-latest/tests/benchmarks/app_kernel/
DREADME.txt8 When the userspace version is selected (CONF_FILE=prj_user.conf), this
/Zephyr-latest/doc/develop/
Denv_vars.rst176 .. envvar:: CONF_FILE
/Zephyr-latest/doc/releases/
Dmigration-guide-3.6.rst34 * Build type by setting ``CONF_FILE`` to ``prj_<build>.conf`` is now deprecated, users should
Drelease-notes-3.6.rst287 * Deprecated ``CONF_FILE`` ``prj_<build>.conf`` build type.
Drelease-notes-3.3.rst3341 * :github:`51621` - APPLICATION_CONFIG_DIR, CONF_FILE do not always pick up local ``boards/*.conf``
3689 * :github:`41830` - CONF_FILE, OVERLAY_CONFIG parsing expands ``${ZEPHYR_<whatever>_MODULE_DIR}``
Drelease-notes-2.5.rst909 * Fixesd build issue that occurs if CONF_FILE contains multiple file paths
Drelease-notes-2.4.rst956 * :github:`28307` - Can't build bootloader/mcuboot while ``CONF_FILE`` contains multiple files.
/Zephyr-latest/doc/develop/test/
Dtwister.rst322 extra_args: CONF_FILE="prj_br.conf"
344 extra_args: CONF_FILE=prj_single.conf