ABI compliance checker Options

From ISP_RAS

Jump to: navigation, search

Basic Options

  • -h|-help

Print help message.

  • -v|-version

Print version.

  • -l|-library <name>

Library name (without version).
It affects only on the path and the title of the report.

  • -d1|-descriptor1 <path>

Path to the descriptor of 1st library version.

  • -d2|-descriptor2 <path>

Path to the descriptor of 2nd library version.

Extra Options

  • -d|-descriptor_template

Create library descriptor template 'lib_ver.xml' in the current directory.

  • -app|-application <path>

This option allow to specify the application that should be tested for portability
to the new library version.

  • -dump_abi|-dump_info <descriptor_path>

Dump library ABI information using specified descriptor.
This command will create '<library>_<ver1>.abi.tar.gz' file in the directory 'abi_dumps/<library>/'.
You can transfer it anywhere and pass instead of library descriptor.

  • -headers_only

Check header files without shared objects. It is easy to run, but may provide
a low quality report with false positives and without detecting of added/withdrawn interfaces.

  • -symbols_list|-int_list <path>

This option allow to specify a file with a list of interfaces (mangled names in C++)
that should be checked, other library interfaces will not be checked.

Other Options

  • -separately

Check headers individually. This mode requires more time for checking ABI compliance,
but possible compiler errors in one header cannot affect others.

  • -test

Run internal tests. Create two binary-incompatible versions of simple library
and run ABI-Compliance-Checker on it.

  • -time

Enable time measurements.

Personal tools