commit | cdb2ff6ca3b3cf9dc60618dbc58f965be0bd071a | [log] [tgz] |
---|---|---|
author | Giuliano Procida <gprocida@google.com> | Thu Jun 15 16:09:23 2023 +0100 |
committer | Matthias Maennich <maennich@google.com> | Thu Jun 22 22:15:48 2023 +0100 |
tree | a80a520f42b768ac36c825ae6782edb5f0c8d26b | |
parent | b3b692e233fbe3ad2ada8936865c95d0a20b0745 [diff] |
error: use a wrapper object for hexadecimal output PiperOrigin-RevId: 540584755 Change-Id: I9d08b47f61c87768f3b0dabbb3c643d791ca8a81
The STG (symbol-type graph) is an ABI representation and this project contains tools for the creation and comparison of such representations. At present parsers exist for libabigail's ABI XML (C types only) and BTF. The ABI diff tool, stgdiff, supports multiple reporting options.
This software currently depends on libxml2 for XML parsing, on libelf to find .BTF sections and on Linux UAPI headers for BTF types.
To build from source, you will need a few dependencies:
Debian | RedHat |
---|---|
libelf-dev | elfutils-devel |
libxml2-dev | libxml2-devel |
linux-libc-dev | kernel-headers |
Instructions are included for local and Docker builds.
You can build as follows:
$ make
A Dockerfile is provided to build a container with libabigail to easily compile the STG tools:
$ docker build -t stg .
And then enter the container:
$ docker run -it stg
If you want to bind your development code to the container:
$ docker run -it $PWD:/src -it stg
The source code is added to /src
, so when your code is bound you can edit on your host and re-compile in the container.
Note that the Dockerfile can provide a development environment (non multi-stage build with the source code) or a production image (a multi-stage build with only the final binary). By default we provide the first, and you can uncomment the final lines of the file for the latter.
See CONTRIBUTING.md for details.