## Release notes

#### Compatibility Analyser – Version 1.9.0

Released 10th December 2009

- Product description
- Main features
- What's new
- Installation notes
- System requirements
- Compatibility issues
- Known issues

### Product description

The Compatibility Analyser tool compares a set of files in two different versions of Symbian releases against a predefined Binary Compatibility (BC) criteria, and reports any changes that affect BC. The analysis is done on header files or import libraries of the platform source code.

The Compatibility Analyser tool is integrated to the Carbide.c++ IDE and provides a Graphical User Interface (GUI) to the tool's core components, BCTools script package. In addition to using the default files that are delivered with the Carbide tool, you can also use core components, for example, from a Web server.

Compatibility reports can be filtered so that they compare the found issues against a knownissues.xml file. This file shows whether or not the same BC problems have occurred before in the Symbian platform.

Both the core components and knownissues.xml files can be retrieved from a Web server to use the latest versions. This ensures that the results of your BC analysis are always up-to-date and do not show, for example, known issues that are already fixed in the platform.

### Main features

- UI for analysing header files, library files, or both types at the same time.
- UI for filtering existing reports generated by the core components.
- UI for selecting the current release and baseline SDKs. The tool automatically displays the SDKs installed in your local file system.
- UI for selecting core components from different places, for example, a Web server.
- UI for specifying the used knownissues.xml files from different locations, for example, a Web server.
- Support for analysing DLL files.
- Support for specifying forced header files, multiple header directories and multiple library directories.
- Support for opening the report files in an XML editor.
- Support for fetching User, System Includes and Forced Headers automatically from the provided bld.inf path in the Baseline Editor.
- Predefined baseline profiles for Symbian SDK Version 3.0, 3.1, 3.2 and 5.0 releases.
- Possibility to run analysis on a selected sub-folder of a project, in addition to the entire project.
- The tool supports GCCE toolchain (tested with CSL Arm Toolchain) and RVCT toolchain.
- The tools does not support WIN*, "TOOLS* target types.
- Supports Symbian OS versions 9.x.
- Option to save the settings of an analysis into a configuration file (.comptanalyser) and use this file to re-run the analysis. This saves the time of going through the wizard when there are no changes in the configuration.

### What's new

- Change: Added option to view the comparison of baseline and current header files.
- Change: Added option to open MMP or source file corresponding to the selected library issue.
- Change: Sharing common data between plug-in & core is done through a common data file in core tools package.
- Change: Changed the meta data file format for predefined baselines in web server.

### Installation notes

- N/A

### System requirements

Basic requirements:

- Windows 2000, Windows XP, Windows Vista
- Minimum one SDK on local PC
- RVCT or GCCE toolchain for ordinal (library) analysis

Additional requirements:

- Python 2.4–2.x

### Compatibility issues

The tool supports the following file types:

- Headers: .h, .hpp, .hrh, .mbg, .pan, .rsg
- Libraries: .dll, .dso

### Known issues

- The Use core components from the SDK option is not valid in preferences.

### Version history

##### Version 2.0 – Day Month Year

- Feature: Added a new feature.
- Change: Changed an existing feature.
- Fix: Fixed a bug.
- Doc: Updated the help based on the latest changes.

##### Version 1.8.0 – 14th October 2009

- Change: Usability improvements for the Analysis Wizard UI.
- Change: Issues for the selected report file will be listed in the right side tree in the Compatibility Analyser view.
- Change: Added option to open a file that has issues.
- Change: Added predefined baseline support for 5.0 public SDK.

##### Version 1.7.0 – 26th August 2009

- Fix: Bug fixes.

##### Version 1.6.0 – 9th July 2009

- Feature: Added support for analysing libraries from multiple build targets.
- Change: Added option to analyse libraries from the default build target.

##### Version 1.5.0 – 29th April 2009

- Feature: Added support for provision of multiple library directory paths
- Feature: Added support for DLL analysis.

##### Version 1.4.0 – 23rd February 2009 and Version 1.4.1 – 4th March 2009

- Feature: Option to save the settings of an analysis into a configuration file (.comptanalyser) and use this file to re-run the analysis. This saves the time of going through the wizard when there are no changes in the configuration.
- Change: The Compatibility Analyser view has been modified with the following additional fields:
  - Last Modified Time: the value in this field specifies the last modification time of a report by the tool.
  - Report Filtered: the value in this field specifies whether a report has been filtered or not by the tool.

##### Version 1.3.2 – 12th January 2009

- Feature: Option to save the settings of an analysis into a configuration file (.comptanalyser) and use this file to re-run the analysis. This saves the time of going through the wizard when there are no changes in the configuration.
- Change: The Compatibility Analyser view has been modified with the following additional fields:
  - Last Modified Time: the value in this field specifies the last modification time of a report by the tool.
  - Report Filtered: the value in this field specifies whether a report has been filtered or not by the tool.

##### Version 1.3.0 – 19th December 2008 and Version 1.3.1 – 5th January 2009

- Feature: Possibility to save the settings of an analysis into a configuration file (.comptanalyser) and use this file to re-run the analysis.
- Feature: Predefined baseline profiles are provided for S60 3.0, 3.1 and 3.2 releases. When any of these profiles is selected, the tool downloads the relevant header/library files from a Web server. The URL of the server can be configured on the Preferences page. Using these profiles enables you to analyse any Public 3.0, 3.1 and 3.2 SDK without actually installing them.
- Change: Analysis can be run on the selected sub-folder of a project, in addition to the entire project.

##### Version 1.2.0 – 29th October 2008 and Version 1.2.1 – 4th November 2008

- Feature: Predefined baseline profiles are provided for S60 3.0, 3.1 and 3.2 releases. When any of these profiles is selected, the tool downloads the relevant header/library files from a Web server. The URL of the server can be configured on the Preferences page. Using these profiles enables you to analyse any Public 3.0, 3.1 and 3.2 SDK without actually installing them.
- Change: Selection of the baseline SDK is now done on the first wizard page. With this improvement, you can specify both the baseline and current SDK on the same page.
- Change: Analysis can be run on the selected sub-folder of a project, in addition to the entire project.

##### Version 1.1.0 – 4th September 2008 and Version 1.1.1 – 25th September 2008

- Feature: Added UI support for forced header files.
- Feature: Added UI support in Baseline Editor to browse for a bld.inf path. The tool fetches User, System Includes and Forced Headers automatically from the provided bld.inf path.
- Change: Added support for multiple header directories.
- Change: Added support to filter files in Add Files dialog.
- Change: Added option to open report files in an XML editor.

##### Version 1.0.0 – 29th July 2008 and Version 1.0.1 – 22nd August 2008

The first version.