https://github.com/lvc/abi-compliance-checker

A tool for checking backward API/ABI compatibility of a C/C++ library
https://github.com/lvc/abi-compliance-checker

Last synced: 3 months ago
JSON representation

A tool for checking backward API/ABI compatibility of a C/C++ library

• Host: GitHub
• URL: https://github.com/lvc/abi-compliance-checker
• Owner: lvc
• License: lgpl-2.1
• Created: 2012-03-08T21:31:54.000Z (almost 13 years ago)
• Default Branch: master
• Last Pushed: 2023-07-21T03:34:04.000Z (over 1 year ago)
• Last Synced: 2024-01-24T09:27:30.994Z (about 1 year ago)
• Language: Perl
• Homepage: https://lvc.github.io/abi-compliance-checker/
• Size: 1.98 MB
• Stars: 587
• Watchers: 39
• Forks: 116
• Open Issues: 66
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

README

        
ABICC 2.3

=========

ABI Compliance Checker (ABICC) — a tool for checking backward binary and source-level compatibility of a C/C++ software library.

Contents

--------

1. [ About      ](#about)

2. [ Install    ](#install)

3. [ Usage      ](#usage)

4. [ Test suite ](#test-suite)

About

-----

The tool analyzes changes in API/ABI (ABI=API+compiler ABI) that may break binary compatibility and/or source compatibility: changes in calling stack, v-table changes, removed symbols, renamed fields, etc.

The tool can create and compare ABI dumps for header files and shared objects of a library. The ABI dump for a library can also be created by the ABI Dumper tool (https://github.com/lvc/abi-dumper) if shared objects include debug-info.

The tool is intended for developers of software libraries and Linux maintainers who are interested in ensuring backward compatibility, i.e. allow old applications to run or to be recompiled with newer library versions.

The tool is a core of the ABI Tracker and Upstream Tracker projects: https://abi-laboratory.pro/tracker/

The tool is developed by Andrey Ponomarenko.

Install

-------

    sudo make install prefix=/usr

###### Requires

* Perl 5

* GCC C++ (3.0 or newer)

* GNU Binutils

* Ctags

* ABI Dumper (1.1 or newer)

###### Platforms

* Linux

* Mac OS X

* Windows

Usage

-----

###### With ABI Dumper

1. Library should be compiled with `-g -Og` GCC options to contain DWARF debug info

2. Create ABI dumps for both library versions using the ABI Dumper (https://github.com/lvc/abi-dumper) tool:

        abi-dumper OLD.so -o ABI-1.dump -lver 1

        abi-dumper NEW.so -o ABI-2.dump -lver 2

3. You can filter public ABI with the help of additional `-public-headers` option of the ABI Dumper tool

4. Compare ABI dumps to create report:

        abi-compliance-checker -l NAME -old ABI-1.dump -new ABI-2.dump

###### Compile headers

    abi-compliance-checker -lib NAME -old OLD.xml -new NEW.xml

`OLD.xml` and `NEW.xml` are XML-descriptors:

    

        1.0

    

    

        /path/to/headers/

    

    

        /path/to/libraries/

    

###### Adv. usage

For advanced usage, see `doc/index.html` or output of `-help` option.

Test suite

----------

The tool is tested properly in the ABI Tracker and Upstream Tracker projects, by the community and by the internal test suite:

    abi-compliance-checker -test

There are about 100 test cases for C and 200 test cases for C++ API/ABI breaks.