## Selecting header files for analysis

##### Before you start

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:

1. To specify the root directory, you can either:
   - Use the \epoc32\include directory of the previously selected SDK.
   - Select the second option and click Add directory... to choose specific directories.
2. To specify which headers are analysed, you can either:
   - Analyse all the files that are available in the selected SDK. To specify which file types are analysed, you can either:
     - Analyse all supported file types (.h, .hrh, .rsg, .mbg, .hpp, and .pan).
     - Select the second option and choose specific file types for analysis.
   - Select the second option and click Add Files to choose the headers from the selected directory in a separate dialog.

     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.

3. (Optional) To show the files also under sub-directories when you click Add Files, select the Use Recursion check box.
4. (Optional) Click Advanced options... to provide advanced settings.
   - For system include paths of this current other than defaults:

     - 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.

     - Click Add Includes to browse for more include paths.
   - To provide additional forced headers
     - Click Add to choose the forced header files from the provided system include paths.
   - To provide additional information about compile-time dependencies, select the Use dependency data option.

     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.

5. Click Next to either:
   - Select library files, if you chose to analyse them on the first wizard page, or:
   - Configure report file options.

##### Related concepts

- Header and library files in preserving compatibility