Lines Matching full:files
31 The main zephyr repository contains Zephyr's source code, configuration files,
36 The files in the **application directory** link Zephyr and any modules with the
37 application. This directory contains all application-specific files, such as
38 application-specific configuration files and source code.
40 Here are the files in a simple Zephyr application:
55 application files, and links the application directory with Zephyr's CMake
57 such as board-specific configuration files, the ability to run and
66 more devicetree overlays, and other default files are also searched for.
77 Kconfig fragments, and other default files are also searched for.
87 * **main.c**: A source code file. Applications typically contain source files
92 directory**, which contains the files you need to build the application and
274 needed. Make any other changes you need to other files.
323 #. Create your source code files.
327 files and sources.
370 defines the target. You can add as many files as you want with
381 #. Set up any other files you may need, such as :ref:`twister <twister_script>`
382 configuration files, continuous integration files, documentation, etc.
400 ``-D`` command-line switch. If you have multiple overlay files, you should
416 fragment files. Multiple filenames can be separated with either spaces or
422 * :makevar:`EXTRA_CONF_FILE`: Additional Kconfig configuration fragment files.
427 * :makevar:`DTC_OVERLAY_FILE`: One or more devicetree overlay files to use.
428 Multiple files can be separated with semicolons.
432 * :makevar:`EXTRA_DTC_OVERLAY_FILE`: Additional devicetree overlay files to use.
433 Multiple files can be separated with semicolons. This can be useful to leave
435 overlay files.
449 fragments and devicetree overlays (if these files exists, otherwise will fallback to
496 #. If your application uses a configuration file or files other than
498 variable to these files appropriately. If multiple filenames are given,
500 build up configuration fragment files in a modular way when you want to
561 #. Now add any application source files to the 'app' target
581 Kconfig and CMake to let you merge externally built hex files
615 Zephyr will use configuration files from the application's configuration
616 directory except for files with an absolute path provided by the arguments
695 Kconfig fragments and board overlays but with a fallback so that if such files do not exist, the
696 files without these suffixes will be used instead.
734 Application-specific source code files are normally added to the
736 number of files the developer can group them into sub-directories
752 be useful for glue code to have access to Zephyr kernel header files.
782 two stages <cmake-details>`. First, build files (also known as a buildsystem)
787 source files and generate an image. To learn more about these concepts refer to
880 The most notable files in the build directory are:
885 generated build system, and where most generated files are created and
888 After running ``ninja``, the following build output files will be written to
902 * Various object files (:file:`.o` files and :file:`.a` files) containing
917 rebuild and test after any major changes to the application's source files,
918 CMakeLists.txt files, or configuration settings.
927 because it fails to recompile one or more necessary files. You can force
936 files, except for the :file:`.config` file that contains the
950 generated files, including the :file:`.config` files that contain
978 support files to make minor adjustments to a board configuration without
979 duplicating all the files described in :ref:`create-your-board-directory` for
1038 The Zephyr build system integrates with the board support files to
1162 Documentation (under ``doc/``) and support files (under ``support/``) are optional, but
1166 Zephyr board, and provide the following files::
1226 which contain SoC support files.
1228 Following the structure above, the following files can be added to load
1241 The Kconfig files above may describe the SoC or load additional SoC Kconfig files.
1243 An example of loading ``stm31l0`` specific Kconfig files in this structure:
1306 directories contain files that can be included from DT sources.
1330 include files that can be located in a ``DTS_ROOT`` directory. By
1331 convention devicetree include files have a ``.dtsi`` extension.