Lines Matching full:files
28 The files in the **application directory** link Zephyr with the
29 application. This directory contains all application-specific files, such as
45 application files, and links the application directory with Zephyr's CMake
47 such as board-specific kernel configuration files, the ability to run and
50 * **Kernel configuration files**: An application typically provides a
58 * **Application source code files**: An application typically provides one
59 or more application-specific files, written in C or assembly language. These
60 files are usually located in a sub-directory called :file:`src`.
62 Once an application has been defined, you can use CMake to create project files
63 for building it from a directory where you want to host these files. This is
79 At the top of the tree there are several files that are of importance:
106 * architecture-specific kernel source files
107 * architecture-specific kernel include files for private APIs
110 SoC related code and configuration files.
113 Board related code and configuration files.
116 Zephyr technical documentation source files and tools used to
123 :ref:`devicetree <dt-guide>` source files used to describe non-discoverable
127 Include files for all public APIs, except those defined under :file:`lib`.
143 Various programs and other files used to build and test Zephyr
205 files and sources.
318 Option 3: Using ``zephyrrc`` files
361 - loads any settings from the ``zephyrrc`` files described above in
395 ``-D`` command-line switch. If you have multiple overlay files, you should
411 fragment files. Multiple filenames can be separated with either spaces or
417 * :makevar:`OVERLAY_CONFIG`: Additional Kconfig configuration fragment files.
422 * :makevar:`DTC_OVERLAY_FILE`: One or more devicetree overlay files to use.
423 Multiple files can be separated with semicolons.
469 #. If your application uses a configuration file or files other than
472 :makevar:`CONF_FILE` variable to these files appropriately.
475 files in a modular way when you want to avoid setting :makevar:`CONF_FILE`
535 #. Now add any application source files to the 'app' target
555 Kconfig and CMake to let you merge externally built hex files
616 Application-specific source code files are normally added to the
618 number of files the developer can group them into sub-directories
634 be useful for glue code to have access to Zephyr kernel header files.
664 two stages <cmake-details>`. First, build files (also known as a buildsystem)
669 source files and generate an image. To learn more about these concepts refer to
769 The most notable files in the build directory are:
774 generated build system, and where most generated files are created and
777 After running ``ninja``, the following build output files will be written to
791 * Various object files (:file:`.o` files and :file:`.a` files) containing
806 rebuild and test after any major changes to the application's source files,
807 CMakeLists.txt files, or configuration settings.
816 because it fails to recompile one or more necessary files. You can force
825 files, except for the :file:`.config` file that contains the
839 generated files, including the :file:`.config` files that contain
867 support files to make minor adjustments to a board configuration without
868 duplicating all the files described in :ref:`create-your-board-directory` for
927 The Zephyr build system integrates with the board support files to
1157 Documentation (under ``doc/``) and support files (under ``support/``) are optional, but
1161 Zephyr board, and provide the following files::
1224 which contain SoC support files.
1226 Following the structure above, the following files can be added to load
1238 The Kconfig files above may describe the SoC or load additional SoC Kconfig files.
1240 An example of loading ``stm31l0`` specific Kconfig files in this structure:
1303 directories contain files that can be included from DT sources.
1327 include files that can be located in a ``DTS_ROOT`` directory. By
1328 convention devicetree include files have a ``.dtsi`` extension.
1398 :file:`.project`, in addition to the usual ninja build files.