Capability map¶
The SDK provides host tools and application-linked native libraries for ARMv5T and ARMv6. Link only the components your application uses.
| Area | Available facilities | Read next |
|---|---|---|
| Build tools | ARM ELF to E32 conversion, frozen-ordinal import proxies, executable and DLL inspection | Building, SDK |
| C++ runtime | libc++ containers, ownership, clocks, compiler-rt helpers and runtime profiles | Guest runtime, C++ usage |
| Concurrency | Futures, Tasks, channels, fibers, timers, property watches and event/worker executors | Concurrency |
| Device APIs | Counters, power and display snapshots, file streaming, camera discovery and TCP sockets | Device APIs |
| Application UI | Native Window Server applications; a guest Qt 4.8.1 widget example with separately supplied Qt DLLs | GUI app, Qt app |
| HTTP and WebSockets | Streaming HTTP/1.1 and HTTP/2 client/server; RFC 8441 WebSockets | HTTP, WebSockets |
| TLS | Mbed TLS 1.2/1.3 sessions with explicit trust roots and peer verification | TLS guide |
| Packaging | SIS generation, application resources, signatures and emulator installation | Packaging |
| EKA1 | Separate legacy executable startup and selected EUSER imports | EKA1 profile |
The modern runtime and device libraries require the EKA2 application ABI. EKA1 has a smaller, separate profile. TLS requires a target-specific secure entropy source. Sensors and media have no exported modern API yet.
Use the C++ reference for symbol details and the linked guides for each component's requirements and restrictions.