|
SafeAPI Backend POSIX
POSIX/Linux OAL backend for safeAPIFreamwork
|
The POSIX/Linux OAL (Operating system Abstraction Layer) backend for safeAPIFreamwork — a real, working implementation of the backend contract safeAPIFreamwork's ADR-018/ADR-005 define: a backend is an integrator-supplied implementation, not part of the reusable safety framework itself, so it lives in its own project rather than inside the framework.
Establishes the naming convention safeAPIBackend<OS> for any future backend (safeAPIBackendQNX, safeAPIBackendFreeRTOS, …) — only this POSIX one exists today as a real implementation; the others are documented conventions, not scaffolded placeholders, until there's something real to build.
safeAPIRBC2oo2GP calls directly into this backend's public headers (sapi_posix_backend_register_all(), sapi_posix_backend_reboot_set_argv()) — the sanctioned ADR-005 registration seam, an ordinary one-directional static-linking dependency (no circular-callback indirection needed, unlike the GP↔GA boundary). Backend behaviour is reached through the framework's own OAL vtables (e.g. sapi_platform_realtime_init()), not by calling this project's functions directly, except at that one registration point.
Same dual-mode consumption of safeAPIFreamwork every SAPI C project uses: