commit | 59f71de6ae087909cf611ad96e8c3e68d53dcaee | [log] [tgz] |
---|---|---|
author | Giuliano Procida <gprocida@google.com> | Mon Jun 26 08:38:21 2023 +0100 |
committer | Matthias Maennich <maennich@google.com> | Fri Jun 30 18:10:53 2023 +0100 |
tree | f1f912863627e180fb692bd73ce068c2c369f42b | |
parent | 24131f7450664c19f175fa355255ef3187dc8cc3 [diff] |
graph: add Limit method This exposes the next node ID that would be allocated. This is a prerequisite for allowing the dense data structures to be sized independently from `Graph`. PiperOrigin-RevId: 543356285 Change-Id: I0b658ab14df8a20f8893e91481881c8cb4bced5c
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.