SDL3 implementation boundary
Section titled “SDL3 implementation boundary”Inno.Native.Sdl3 is the backend implementation used by the engine’s SDL3 platform adapter. Application code uses the engine’s window, event and input contracts. Start with SDL3 integration or reading input.
Shared ABI contract
Section titled “Shared ABI contract”Product preparation selects matching managed bindings, native payloads and runtime inputs for the target. A generated declaration is not proof that the corresponding deployment is valid. The adapter owns window lifetime, event routing and owner-thread access; raw addresses do not replace those protections.
Keep module access available through resource cleanup. Static and dynamic linkage are explicit product choices, not a fallback search through arbitrary build caches. Build artifacts and deployment explains the engine’s producer and consumer responsibilities.
Documentation scope
Section titled “Documentation scope”Third-party SDL functions, structures, enums and generated bindings are not part of this engine documentation. Use the pinned upstream SDL material when working inside the native implementation. The original SDL license is retained unchanged.