Searched refs:candidates (Results 1 – 10 of 10) sorted by relevance
46 # to locate in-project-tree Zephyr candidates.71 # a list of all potential Zephyr candidates in the tree to consider.74 # The find package will also find ourself when searching using installed candidates.84 # Check is done in Zephyr workspace already, thus check only for pure Zephyr candidates.
111 # Only do this if we are an installed CMake Config package and checking for workspace candidates.125 # Checking for installed candidates which could also be an workspace candidates.134 # Check for workspace candidates.138 # Ending here means there were no candidates in workspace of the app.
154 # Ending here means there were no candidates in workspace of the app.
21 # Did we find any candidates ?45 message(WARNING "Multiple sysroot candidates found: ${sysroot_candidates_str}\n"
24 stabilization phase. Release candidates will be tagged during the66 of the release candidates. For the codebase release which is destined to be134 the candidates to be promoted to blocker bugs
185 CMake will search all exported candidates to find a Zephyr installation which matches this version441 Common file used for detection of Zephyr repository and workspace candidates.
60 :zephyr:board:`ch32v003evt`, several boards with CAN+USB capabilities making them good candidates
1495 the state to ``PTHREAD_EXITED``. Consider both states as candidates in
632 Potential candidates are confidential information such as
374 New modules, that are candidates for being included in the Zephyr
