Native C++ reference¶
The reference is easiest to use after choosing the layer your code touches. The SDK owns application services and build tools; original Symbian headers describe OS interfaces that an application may call through verified imports. The SDK native API guide explains targets, results and lifetime before the generated symbol detail.
| What you are doing | Read first | Symbol detail |
|---|---|---|
| Writing an application | C++ usage and runtime support | SDK C++ API |
| Using display, storage, power or camera services | Device API map | SDK C++ API |
| Inspecting E32 or SIS artifacts on the host | SDK exports | SDK C++ API |
| Calling EUSER, Window Server or file APIs directly | Native Symbian interfaces | Original header reference |
How to read the generated pages¶
The SDK C++ reference has a task-oriented landing page,
namespace index, file list and searchable declarations. Start with a public
header: symbian/api/... for guest services, symbian/concurrency/... for
asynchronous work, or symbian/e32 and symbian/sis for host format tools.
Implementation files appear to help trace behavior; they are not additional
application APIs.
The original header reference is deliberately separate and covers eleven selected historical headers. Check the SDK import proxy and selected firmware's exports before depending on an OS symbol.