[Bug default/30034] New: [libabigail] Handle library splitting

["david.marchand at redhat dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30034

            Bug ID: 30034
           Summary: [libabigail] Handle library splitting
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: david.marchand at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

We have been tracking ABI changes in the DPDK project (which consists of
multiples libraries).
One of the DPDK libray, the "EAL", which is kind of central and which is linked
by _all_ applications using DPDK, has become bloated.. and we are looking into
splitting it.


Our problem is that since we compare the EAL shared library to a reference
build, moving code to a new library (which EAL depends on) results in abidiff
complaining about missing symbols, since they are not exposed anymore as part
of the EAL scope.

It would be nice if libabigail came with a way to deal with this.
Some ideas:
- handle multiple abi-corpus in the existing tools (in our case, the splitted
libraries dumps would be concatenated to a single xml file and passed to
abidiff)?
- add some option to automatically follow DT_NEEDED entries?
- add another tool that would make it possible to compare a set of libraries
exported interface in one go?


Note: for the DT_NEEDED idea, it might be interesting to be able to filter
which DT_NEEDED entries are followed (like for example with a
"--follow-dt-needed librte_" option) so that we can only monitor changes in a
set of libraries (iow, in this option example, the libraries matching the
regexp "librte_").

-- 
You are receiving this mail because:
You are on the CC list for the bug.