Searched refs:CMake (Results 1 – 25 of 150) sorted by relevance
123456
| /Zephyr-Core-3.6.0/cmake/modules/ |
| D | zephyr_default.cmake | 5 # This CMake module will load all Zephyr CMake modules in correct order for
9 # See individual CMake module descriptions
13 # The code line below defines the real minimum supported CMake version.
15 # Unfortunately CMake requires the toplevel CMakeLists.txt file to define the
16 # required version, not even invoking it from a CMake module is sufficient.
22 # Different CMake versions can have very subtle differences, for
23 # instance CMake 3.21 links object files in a different order compared
24 # to CMake 3.20; this produces different binaries.
25 message(STATUS "CMake version: ${CMAKE_VERSION}")
53 # Test and error-out if we are affected by the PyPI CMake 3.22.1 / 3.22.2 bug
[all …]
|
| D | doc.cmake | 5 # This CMake module will load all Zephyr CMake modules required for a
8 # The following CMake modules will be loaded:
|
| D | root.cmake | 7 # This CMake module will convert all relative paths in existing ROOT lists to
11 # - ARCH_ROOT: CMake list of arch roots containing arch implementations
12 # - SOC_ROOT: CMake list of SoC roots containing SoC implementations
13 # - BOARD_ROOT: CMake list of board roots containing board and shield implementations
14 # - MODULE_EXT_ROOT: CMake list of module external roots containing module glue code
|
| D | arch.cmake | 7 # This CMake module will set the following variables in the build system based
13 # The following variables will be defined when this CMake module completes:
20 # - ARCH_ROOT: CMake list of arch roots containing arch implementations
21 # - BOARD_DIR: CMake variable specifying the directory of the selected BOARD
|
| D | zephyr_module.cmake | 53 # ZEPHYR_MODULES was provided as argument to CMake.
80 # a setting. The use of quotes is required due to CMake not supporting
98 # one module. The use of quotes is required due to CMake not supporting
111 # one module. The use of quotes is required due to CMake not supporting
131 # one Zephyr module. The use of quotes is required due to CMake not
146 \${ZEPHYR_${MODULE_NAME_UPPER}_MODULE_DIR} CMake variable.")
152 # one Zephyr module. The use of quotes is required due to CMake not
166 \${SYSBUILD_${MODULE_NAME_UPPER}_MODULE_DIR} CMake variable.")
|
| D | kernel.cmake | 5 # Zephyr Kernel CMake module.
7 # This is the main Zephyr Kernel CMake module which is responsible for creation
10 # This CMake module creates 'project(Zephyr-Kernel)'
29 # find_package(Zephyr) then it won't be loading any Zephyr CMake modules by itself.
32 BRIEF_DOCS "Global list of all Zephyr CMake libs that should be linked in"
33 FULL_DOCS "Global list of all Zephyr CMake libs that should be linked in.
90 # CMake's 'project' concept has proven to not be very useful for Zephyr
124 "Export CMake compile commands. Used by gen_app_partitions.py script"
140 # Testing the toolchain flags requires the enable_language() to have been called in CMake.
208 # "app" is a CMake library containing all the application code and is
|
| /Zephyr-Core-3.6.0/doc/build/ |
| D | zephyr_cmake_package.rst | 3 Zephyr CMake Package
6 The Zephyr `CMake package`_ is a convenient way to create a Zephyr-based application.
12 The Zephyr CMake package ensures that CMake can automatically select a Zephyr installation to use f…
20 To use the Zephyr CMake package it must first be exported to the `CMake user package registry`_.
22 CMake user package registry.
29 In Linux, the CMake user package registry is found in:
35 In macOS, the CMake user package registry is found in:
41 In Windows, the CMake user package registry is found in:
43 ``HKEY_CURRENT_USER\Software\Kitware\CMake\Packages\Zephyr``
46 The Zephyr CMake package allows CMake to automatically find a Zephyr base.
[all …]
|
| /Zephyr-Core-3.6.0/share/sysbuild/ |
| D | CMakeLists.txt | 12 # If APP_DIR is a relative path, then CMake will adjust to absolute path based
17 # sysbuild CMake modules with general Zephyr CMake modules.
19 # List of Zephyr and sysbuild CMake modules we need for sysbuild.
20 # Note: sysbuild_kconfig will internally load kconfig CMake module.
|
| /Zephyr-Core-3.6.0/share/zephyr-package/cmake/ |
| D | zephyr_export.cmake | 3 # Purpose of this CMake file is to install a ZephyrConfig package reference in:
15 …"HKEY_CURRENT_USER\\Software\\Kitware\\CMake\\Packages\\Zephyr\;${MD5_SUM}" "${CMAKE_CURRENT_LIST_…
24 message("HKEY_CURRENT_USER\\Software\\Kitware\\CMake\\Packages\\Zephyr\n")
|
| D | ZephyrConfig.cmake | 13 # Internal Zephyr CMake package message macro.
15 # This macro is only intended to be used within the Zephyr CMake package.
20 # Arguments to zephyr_package_message() are identical to regular CMake message()
30 "The directory containing a CMake configuration file for Zephyr." FORCE
34 zephyr_package_message(DEPRECATION "The ZephyrUnittest CMake package has been deprecated.\n"
35 "ZephyrUnittest has been replaced with Zephyr CMake module 'unittest' \n"
135 # CMake finds packages will look all packages registered in the user package registry.
138 # and if so, we will return here, and let CMake call into the other registered package for real
156 # CMake find_package has already done the version checking, so let's just include boiler plate.
|
| D | ZephyrConfigVersion.cmake | 5 # The purpose of the version file is to ensure that CMake find_package can correctly locate a
60 # Zephyr uses project version, but CMake package uses PACKAGE_VERSION
97 # Zephyr uses project version, but CMake package uses PACKAGE_VERSION
111 # Only do this if we are an installed CMake Config package and checking for workspace candidates.
127 # CMake finds packages will look all packages registered in the user package registry.
130 # will return here, and let CMake call into the other registered package for
140 # Let's do basic CMake version checking.
|
| /Zephyr-Core-3.6.0/share/zephyrunittest-package/cmake/ |
| D | zephyr_export.cmake | 3 # Purpose of this CMake file is to install a ZephyrUnittestConfig package reference in:
15 …"HKEY_CURRENT_USER\\Software\\Kitware\\CMake\\Packages\\ZephyrUnittest\;${MD5_SUM}" "${CMAKE_CURRE…
24 message("HKEY_CURRENT_USER\\Software\\Kitware\\CMake\\Packages\\ZephyrUnittest\n")
|
| /Zephyr-Core-3.6.0/cmake/ |
| D | package_helper.cmake | 6 # to the Zephyr CMake package and module structure.
9 # build tool that is executed during CMake configure time without creating a
12 # It does so by loading the Zephyr CMake modules specified with the 'MODULES'
15 # This script executes the given module identical to Zephyr CMake configure time.
22 # For example, if you were invoking CMake for 'hello_world' sample as:
30 # If you invoke CMake for 'hello_world' as:
48 # However, several Zephyr CMake modules create custom target for user convenience
114 # Loading Zephyr CMake extension commands, which allows us to overload Zephyr
119 # However, custom targets cannot be used in CMake script mode.
|
| /Zephyr-Core-3.6.0/cmake/toolchain/xcc/ |
| D | generic.cmake | 15 # However, CMake doesn't recognize it when invoking through xt-xcc.
16 # This results in CMake going through all possible combinations of
19 # lengthens the CMake phase of build, especially when XCC needs to
|
| /Zephyr-Core-3.6.0/cmake/compiler/xcc/ |
| D | target.cmake | 5 # Configures CMake for using GCC, this script is re-used by several
17 # with C++ support just set it to something so CMake doesn't
49 # For CMake to be able to test if a compiler flag is supported by the
50 # toolchain we need to give CMake the necessary flags to compile and
53 # CMake checks compiler flags with check_c_compiler_flag() (Which we
|
| /Zephyr-Core-3.6.0/cmake/toolchain/armclang/ |
| D | generic.cmake | 10 "doesn't work properly for target object files on CMake version: "
11 "${CMAKE_VERSION}. Use the 'Ninja' generator or update to CMake >= 3.21."
|
| /Zephyr-Core-3.6.0/include/zephyr/linker/ |
| D | app_smem.ld | 4 * This hackish way of including files is due to CMake issues:
8 * When using the "Unix Makefiles" generator, CMake simply
24 * hackish needs to be used since CMake does not parse
|
| D | app_smem_pinned.ld | 8 * This hackish way of including files is due to CMake issues:
12 * When using the "Unix Makefiles" generator, CMake simply
28 * hackish needs to be used since CMake does not parse
|
| /Zephyr-Core-3.6.0/soc/xtensa/nxp_adsp/common/ |
| D | CMakeLists.txt | 1 # NXP SoC family CMake file
|
| /Zephyr-Core-3.6.0/cmake/compiler/host-gcc/ |
| D | target.cmake | 3 # Configures CMake for using GCC
14 # with C++ support just set it to something so CMake doesn't
|
| D | generic.cmake | 3 # Configures CMake for using GCC
|
| /Zephyr-Core-3.6.0/lib/libc/newlib/ |
| D | CMakeLists.txt | 49 # CMake is capable of handling circular link dependencies for CMake defined
51 # However, libc and libgcc are not regular CMake libraries, and is seen as linker
52 # flags by CMake, and thus symbol de-duplications will be performed.
53 # CMake link options cannot be used, as that will place those libs first on the
|
| /Zephyr-Core-3.6.0/doc/develop/sca/ |
| D | index.rst | 6 Support for static code analysis tools in Zephyr is possible through CMake.
34 └── sca.cmake # CMake code that configures the tool to be used with Zephyr
50 :makevar:`SCA_TOOL` can be set as a regular CMake setting using
|
| /Zephyr-Core-3.6.0/soc/xtensa/intel_adsp/ |
| D | CMakeLists.txt | 1 # Intel ADSP SoCs family CMake file
|
| /Zephyr-Core-3.6.0/doc/build/sysbuild/ |
| D | index.rst | 20 CMake and uses :ref:`Kconfig <kconfig>`.
37 Every Zephyr CMake build system managed by sysbuild.
40 When more than one Zephyr CMake build system (domain) is managed by sysbuild.
131 Here is an example using CMake and Ninja.
141 To use sysbuild directly with CMake, you must specify the sysbuild
143 an extra CMake argument. ``APP_DIR`` is the path to the main Zephyr
149 When building a single Zephyr application without sysbuild, all CMake cache
190 CMake variable namespacing
193 CMake variable settings can be passed to CMake using ``-D<var>=<value>`` on the
194 command line. You can also set Kconfig options via CMake as
[all …]
|
123456
