Lines Matching full:files

263 All source files in a module's codebase shall include a license header,
265 files that do not include license headers.
267 Main license files shall be added in the module's codebase by Zephyr
269 and they contain a permissive OSI-compliant license. Main license files
271 SPDX license identifier. If multiple main license files are present it
275 Individual license headers in module source files supersede the main license.
283      headers and main license files. This not a hard requirement; should
286      multiple main license files), this practice may be accepted by and
295 * import the main license files, if they exist in the external project, and
381 contain :file:`CMakeLists.txt` and :file:`Kconfig` files describing how to
382 build and configure them, respectively. Module :file:`CMakeLists.txt` files are
384 :file:`Kconfig` files are included in the build's Kconfig menu tree.
452 Module integration files (in-module)
455 Inclusion of build files, :file:`CMakeLists.txt` and :file:`Kconfig`, can be
471 :file:`CMakeLists.txt` and :file:`Kconfig` files in the root directory of the
512 In Kconfig, the variable may be used to find additional files to include.
526 processing. The module can source additional CMake files using these ``CURRENT``
579 Module integration files (external)
582 Module integration files can be located externally to the Zephyr module itself.
584 files located externally to Zephyr modules.
586 Module integration files in Zephyr
590 files for certain known Zephyr modules.
592 Those files are located under
602 Module integration files in a custom location
631    This allows you to overrule any integration files under
636 integration files for Zephyr modules via specifically named CMake variables.
664 Module integration files (zephyr/module.yml)
668 that the build files, :file:`CMakeLists.txt` and :file:`Kconfig`, are located
671 Build files located in a ``MODULE_EXT_ROOT`` can be described as:
699 - ``dts_root``: Contains additional dts files related to the architecture/soc
700   families. Additional dts files must be located in a :file:`<dts_root>/dts`
707 - ``module_ext_root``: Contains :file:`CMakeLists.txt` and :file:`Kconfig` files
744 boards, the module file can point twister to the path where those files
772 just those projects which have the necessary module metadata files.
777   content of that file will be used to determine which files should be added
782   :file:`zephyr/Kconfig` files in the project. If both are present, the project
783   is considered a module, and those files will be added to the build.
796 either a :file:`zephyr/module.yml` file or the files
872 module related files and changes in relation to upstream need to be maintained