Working example

In this example, we would measure the binary compatibility for a fictional component by name Alice. The modified component is called Alice'.

The GXP for Alice is built as outlined in Building GXP files, the files are created in epoc32\release\gccxml\urel. Remove all the unwanted GXP files from this directory to simplify the comparison of the component. Extract the data related to Alice into the first database.

> cdb –d c:\old\cdb.db extractrelease alice_old

This extracts data about the old Alice component into a configuration called alice_old which resides in a database located in c:\old\cdb.db.

The GXP for the modified Alice (Alice') is built as outlined in Building GXP files, files are created in epoc32\release\gccxml\urel. As with the old component, we remove all the unwanted GXP files to limit the scope of the comparison.

> cdb –d c:\new\cdb.db extractrelease alice_new

This extracts data about the new Alice component into a configuration called alice_new which resides in a database located in c:\new\cdb.db.

Assuming that the data about components that need to be compared is extracted to the database, compare the old and new versions of Alice.

> cdb –d c:\old\cdb.db comparerelease alice_old –a c:\new\cdb.db alice_new –r c:\report.xml

This compares the release called alice_old which can be found in c:\old\cdb.db with the release called alice_new which can be found in c:\new\cdb.db.

To generate a report containing the comparisons, provide, -r flag option. This indicates that the report must be generated, named report.xml and saved in C drive. The report is stored in both XML and HTML formats for the user to read and check.

When databases are no longer needed, delete the two databases manually, from their directories.