Lines Matching full:posix

6 In many ways, Zephyr provides support like any POSIX OS; API bindings are provided in the C
7 programming language, POSIX headers are available in the standard include path, when configured.
9 Unlike other multi-purpose POSIX operating systems
11 - Zephyr is not "a POSIX OS". The Zephyr kernel was not designed around the POSIX standard, and
12   POSIX support is an opt-in feature
16 - Zephyr does not provide a POSIX shell, compiler, utilities, and is not self-hosting.
26 As a library, Zephyr's POSIX API implementation makes an effort to be a thin abstraction layer
31 - The POSIX interface and implementations should be part of Zephyr's POSIX library, and not
32   elsewhere, unless required both by the POSIX API implementation and some other feature. An
33   example where the implementation should remain part of the POSIX implementation is
37 - When the POSIX API and another Zephyr subsystem both rely on a feature, the implementation of
38   that feature should be as a separate Zephyr library that can be used by both the POSIX API and
46    :caption: Dependency cycle between POSIX and another Zephyr library
60    :caption: Mutual dependencies between POSIX and other Zephyr libraries
75 - POSIX API calls should be provided as regular callable C functions; if a Zephyr
77   implementation of that system call should be hidden behind the POSIX API.