Use RELEASEINFO
command to get the information about the
release that is currently in the database.
> cdb RELEASEINFO
Use EXTRACTRELEASE
to extract a SINGLE release to the
database. This reads in all files in epoc32\include\...
to the
database, and assigns the configuration name to the extracted files.
> cdb extractrelease <config> [-a <api_doc>]
where:
<config>
is the configuration name of the
extracted data
-a <api_doc>
is the full path to the API
classification document. This option provides the access information i.e. if
the API is symbian internal, published all or published partners, and status
information that is if the API is released, depricated or unspecified
etc.
Use COMPARERELEASE
to check the compatibility of the code
in the current database or across databases.
> cdb compare <baseconfig> -a <alt db> <derivedconfig> [-r <report>] [-x <xsl_doc>] [-f <apilevel>]
where:
<baseconfig>
is the configuration that
establishes the compatibility standard
-a <alt db>
is the full path to the second
database against which comparisons will be made.
<derivedconfig>
is the configuration that is to
be tested for compatbility with the <baseconfig>
-r <report>
is the report prefix to use for
generated reports
-x <xsl_doc>
is the name of the
xslt
document to use to transform the XML to HTML.
-f <apilevel>
is the lowest API classification
which will be reported, e.g published All, internalTechnology.