Searched refs:CMake (Results 1 – 25 of 184) sorted by relevance
12345678
| /Zephyr-latest/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
15 # - SCA_ROOT: CMake list of SCA roots containing static code analysis integration code
|
| D | arch_v1.cmake | 6 # This CMake module is only valid for hw model v1.
11 # This CMake module will set the following variables in the build system based
17 # The following variables will be defined when this CMake module completes:
24 # - ARCH_ROOT: CMake list of arch roots containing arch implementations
25 # - BOARD_DIR: CMake variable specifying the directory of the selected BOARD
|
| D | arch_v2.cmake | 8 # This CMake module will set the following variables in the build system based
14 # The following variables will be defined when this CMake module completes:
21 # - ARCH_ROOT: CMake list of arch roots containing arch implementations
|
| 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.")
|
| /Zephyr-latest/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-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_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
15 # - SCA_ROOT: CMake list of SCA roots containing static code analysis integration code
21 # Converted paths are placed in the CMake cache so that they are propagated
|
| /Zephyr-latest/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.
|
| /Zephyr-latest/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-latest/cmake/toolchain/xt-clang/ |
| D | generic.cmake | 11 # However, CMake doesn't recognize it when invoking through xt-clang.
12 # This results in CMake going through all possible combinations of
15 # lengthens the CMake phase of build, especially when xt-clang needs to
|
| /Zephyr-latest/cmake/toolchain/xcc/ |
| D | generic.cmake | 16 # However, CMake doesn't recognize it when invoking through xt-xcc.
17 # This results in CMake going through all possible combinations of
20 # lengthens the CMake phase of build, especially when XCC needs to
|
| /Zephyr-latest/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
54 # For CMake to be able to test if a compiler flag is supported by the
55 # toolchain we need to give CMake the necessary flags to compile and
58 # CMake checks compiler flags with check_c_compiler_flag() (Which we
|
| /Zephyr-latest/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:
|
| /Zephyr-latest/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-latest/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-latest/soc/nxp/imx/imx8ulp/adsp/ |
| D | CMakeLists.txt | 1 # NXP SoC family CMake file
|
| /Zephyr-latest/soc/nxp/imx/imx8x/adsp/ |
| D | CMakeLists.txt | 1 # NXP SoC family CMake file
|
| /Zephyr-latest/soc/nxp/imx/imx8/adsp/ |
| D | CMakeLists.txt | 1 # NXP SoC family CMake file
|
| /Zephyr-latest/soc/nxp/imx/imx8m/adsp/ |
| D | CMakeLists.txt | 1 # NXP SoC family CMake file
|
| /Zephyr-latest/doc/develop/tools/ |
| D | clion.rst | 9 the IDE's CMake integration. This approach is no longer optimal.
13 valid if you prefer to use CMake.
55 Configure the toolchain and CMake profile
58 CLion will open the :guilabel:`Open Project Wizard` with the CMake profile settings. If that does
59 not happen, go to :menuselection:`Settings --> Build, Execution, Deployment --> CMake`.
77 #. Back in the CMake profile settings dialog, specify your board in the :guilabel:`CMake options`
87 :alt: CMake profile
91 CMake load should finish successfully.
112 Note that other CMake targets like ``puncover`` or ``hardenconfig`` can also be called at this
|
| /Zephyr-latest/cmake/compiler/host-gcc/ |
| D | generic.cmake | 3 # Configures CMake for using GCC
|
| /Zephyr-latest/doc/services/serialization/ |
| D | nanopb.rst | 60 Adding ``proto`` files can be done with the ``zephyr_nanopb_sources()`` CMake function which
67 The internal CMake generator has an extension to configure ``*.options.in`` files automatically
68 with CMake variables.
|
12345678
