Lines Matching full:and
3 History and Motivation
9 * The ability to provide an extensible and user-friendly command-line interface
20 along with a clear justification of the choice not to use existing tools and
28 * **R2**: Provide a tool that both Zephyr users and distributors can make use of
29 to benefit from and extend
30 * **R3**: Allow users and downstream distributions to override or remove
32 * **R4**: Support both continuous tracking and commit-based (bisectable) project
40 `Git Submodules <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ and
43 Existing tools were considered during west's initial design and development.
69 an RTOS kernel, and is instead a collection of components that work together.
73 * Clean separation of Zephyr original code and imported projects and libraries
74 * Avoidance of license incompatibilities between original and imported code
75 * Reduction in size and scope of the core Zephyr codebase, with additional
78 * Safety and security certifications
80 * Out-of-tree development based on subsets of the supported boards and SoCs
94 might need to be installed and accessible to the build system). It may not
99 - **Compatible with CMake**: building, flashing and debugging, and
103 - **Cross-platform**: West is written in Python 3, and works on all
113 strong and compelling motivation.
116 commands is clearly specified and documented. This enables
117 interoperability with third party tools, and means Zephyr developers
120 See :github:`Zephyr issue #6205 <6205>` and for more details and discussion.