## File handling in project and folder analysis

Compatibility Analyser can be used to analyse a whole project or files under a specific sub-folder in a project.

Case 1: Analysing the parent project (behaviour is same as when the tool is launched by right-clicking a project)

- Case 1a: The project is an EXE project
  - Only the header analysis option will be checked on the first page of the Compatibility Analyser wizard. (The Use recursion option will be checked.)
  - Header files will be taken from all the USERINCLUDE paths specified in all the MMP files.
  - Platform headers will be taken from all the SYSTEMINCLUDE paths specific in all the MMP files.

  Case 1b: The project is a DLL project

  - Header files will be taken from all the USERINCLUDE paths specified in all the MMP files. (The Use recursion option will be checked.)
  - Platform headers will be taken from all the SYSTEMINCLUDE paths specified in all the MMP files.
  - Library files (.dso) will be added only if the corresponding .dso files exist in the default build target (such as release/armv5/lib) directory of the SDK that is selected as the default configuration.

Case 2: Analysing files under the selected folder

- Only the header analysis option will be checked on the first page of the Compatibility Analyser wizard. (The Use recursion option will be checked.)
- Header files will be taken from the selected folder.
- Platform headers will be taken from all the SYSTEMINCLUDE paths specific in all the MMP files of the parent project.

##### Related Tasks

- Selecting header files for analysis
- Selecting library files for analysis