Home
last modified time | relevance | path

Searched refs:registry (Results 1 – 17 of 17) sorted by relevance

/Zephyr-latest/doc/build/
Dzephyr_cmake_package.rst20 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:
63 Zephyr CMake package is exported to the CMake user package registry using the following commands:
69 This will export the current Zephyr to the CMake user package registry.
132 * Zephyr freestanding application will use the Zephyr registered in the CMake user package registry.
150 registry and therefore this Zephyr will be used by the Zephyr freestanding application
345 installed in the CMake package registry. The search steps are:
[all …]
/Zephyr-latest/share/zephyr-package/cmake/
Dzephyr_export.cmake22 message("has been added to the user package registry in:")
DZephyrConfig.cmake135 # CMake finds packages will look all packages registered in the user package registry.
DZephyrConfigVersion.cmake127 # CMake finds packages will look all packages registered in the user package registry.
/Zephyr-latest/share/zephyrunittest-package/cmake/
Dzephyr_export.cmake22 message("has been added to the user package registry in:")
/Zephyr-latest/subsys/fs/
Dfs.c37 static struct registry_entry registry[CONFIG_FILE_SYSTEM_MAX_TYPES]; variable
49 for (size_t i = 0; i < ARRAY_SIZE(registry); ++i) { in registry_add()
50 struct registry_entry *ep = &registry[i]; in registry_add()
65 for (size_t i = 0; i < ARRAY_SIZE(registry); ++i) { in registry_find()
66 struct registry_entry *ep = &registry[i]; in registry_find()
/Zephyr-latest/doc/develop/west/
Dzephyr-cmds.rst54 config package in the CMake user package registry.
56 In Windows, the CMake user package registry is found in
59 In Linux and MacOS, the CMake user package registry is found in.
/Zephyr-latest/doc/develop/toolchains/
Dzephyr_sdk.rst42 of the Zephyr SDK, then you must register the Zephyr SDK in the CMake package registry
43 by running the setup script. If you decide not to register the Zephyr SDK in the CMake registry,
/Zephyr-latest/dts/bindings/
Dbinding-types.txt4 # Devicetree binding types registry.
Dvendor-prefixes.txt1 # Device tree binding vendor prefix registry. Keep this list in
/Zephyr-latest/doc/connectivity/networking/api/
Dlwm2m.rst228 `LwM2M registry`_.
790 lock :Lock the LwM2M registry
791 unlock :Unlock the LwM2M registry
809 .. _LwM2M registry:
/Zephyr-latest/doc/security/
Dreporting.rst149 .. _Vulnerability Registry: https://www.zephyrproject.org/vulnerability-registry
/Zephyr-latest/doc/develop/getting_started/
Dinstallation_linux.rst277 register the Zephyr SDK in the CMake package registry by running the setup
/Zephyr-latest/doc/develop/
Dbeyond-GSG.rst153 The :ref:`cmake_pkg` can be exported to CMake's user package registry if it has
/Zephyr-latest/doc/releases/
Drelease-notes-2.3.rst655 This allows for registering Zephyr in the CMake user package registry and
658 Registering the Zephyr CMake package in the CMake user package registry
662 registration of Zephyr CMake package in the CMake user package registry.
Drelease-notes-3.2.rst826 * Refactored LwM2M engine module into smaller sub-modules: LwM2M registry,
Drelease-notes-3.3.rst1080 * Added shell command to lock/unlock LwM2M registry.