Before you can add header files for analysis, the type of analysis, baseline profile and the current SDK must be selected first. For instructions, see Selecting the analysis type, baseline profile and current SDK.
Note: Header files are handled differently in EXE and DLL projects. See File handling in project and folder analysis for more information.
To select header files, follow these steps:
Tip: If you know that a file has different names in the current SDK and baseline SDK, click Set baseline filename. In the Set Baseline file dialog, enter the new filename and click OK.
The following table lists the default system include paths supplied by the tool, based on SDK version:
SDK Version | Default System Includes |
Symbian Version 1 and Symbian Version 2 |
epoc32\include |
epoc32\include\ecom | |
epoc32\include\oem | |
epoc32\include\libc | |
epoc32\include\middleware | |
epoc32\include\domain\middleware | |
epoc32\include\osextensions | |
epoc32\include\domain\osextensions | |
epoc32\include\applications | |
epoc32\include\domain\applications | |
epoc32\include\domain\middleware\loc | |
epoc32\include\domain\osextensions\loc | |
epoc32\include\domain\applications\loc | |
epoc32\include\domain\middleware\loc\sc | |
epoc32\include\domain\osextensions\loc\sc | |
epoc32\include\domain\applications\loc\sc |
Disclaimer: The default include paths can be different if non-default core components are in use.
It is recommended to select this option to ensure that all headers are compiled successfully, with the help of platform datafiles. The files are included in the tool's delivery and there are separate files for each Symbian platform version.