Searched refs:dependency (Results 1 – 25 of 74) sorted by relevance
123
9 * greps for "#include" to generate dependency list.11 * in the dependency list. This creates weird dependency20 * Since the dependency list of A.cmd contains both26 * the dependency list. The dependencies should then be
13 * greps for "#include" to generate dependency list.15 * in the dependency list. This creates weird dependency24 * Since the dependency list of A.cmd contains both30 * the dependency list. The dependencies should then be
78 static int llext_dependency_add(struct llext *ext, struct llext *dependency) in llext_dependency_add() argument82 for (i = 0; i < ARRAY_SIZE(ext->dependency); i++) { in llext_dependency_add()83 if (ext->dependency[i] == dependency) { in llext_dependency_add()87 if (!ext->dependency[i]) { in llext_dependency_add()88 ext->dependency[i] = dependency; in llext_dependency_add()89 dependency->use_count++; in llext_dependency_add()102 for (i = 0; i < ARRAY_SIZE(ext->dependency) && ext->dependency[i]; i++) { in llext_dependency_remove_all()107 ext->dependency[i]->use_count--; in llext_dependency_remove_all()108 __ASSERT(ext->dependency[i]->use_count, "LLEXT dependency use-count underrun!"); in llext_dependency_remove_all()
55 # gperf is an optional dependency58 # openocd is an optional dependency61 # bossac is an optional dependency64 # imgtool is an optional dependency (the build may also fall back to scripts/imgtool.py68 # winpty is an optional dependency
7 # west is an optional dependency. We need to run west using the same
19 Use ``apt`` to install dependency:27 Use ``brew`` to install dependency:35 Use ``choco`` to install dependency:
11 # Required to satisfy dependency of networking stack on RNG
5 # Demonstrate that our library includes a generated header so we need the following dependency
8 # using select SPI at this point introduces a cyclic dependency
5 # and do not make it a dependency of anything else.
44 # TODO: Remove dependency on BT_MCC once MCC has been reworked53 # TODO: Remove dependency on BT_MCC_OTS once MCC has been reworked
39 the other library or subsystem. This reduces the likelihood of dependency cycles in code. When42 ``libzfoo`` also depends on ``libposix``, then there is a dependency cycle. The cycle can be43 removed via mutual dependency, ``libcommon``.
27 # used to generate devicetree dependency graphs
41 # dependency between the two targets56 # 'custom_target' for it and setting up a dependency between the two
23 # This ensures that symbols are available in Kconfig for dependency checking
122 struct llext *dependency[LLEXT_MAX_DEPENDENCIES]; member
28 # link dependency to libc (strchr), but libc also has dependencies to libgcc.
35 * The core operations are request (add a dependency) and release (remove36 a dependency). Supporting operations are reset (to clear an error
84 # Add explicit dependency on app target for ZEPHYR_CURRENT_LIBRARY, so these
23 Decoder has internal state since there are dependency between opcodes (e.g. timestamp can be
148 A *dependency ordering* of a devicetree is a list of its nodes, where each node150 *dependency ordinal* is then its zero-based index in that list. Thus, for two151 distinct devicetree nodes ``n1`` and ``n2`` with dependency ordinals ``d1`` and158 The Zephyr build system chooses a dependency ordering of the final devicetree159 and assigns a dependency ordinal to each node. Dependency related information160 can be accessed using the following macros. The exact dependency ordering
56 Will the Zephyr project have a direct dependency on the component, or
116 # This link is needed to resolve circular dependency between SL and platform
