On Tue, Nov 3, 2020 at 11:07 AM Kinsella, Ray <m...@ashroe.eu> wrote: > Came across an issue with this. > > Essentially what is happening is that an ABI dump file generated with a newer > versions of libabigail > is not guaranteed to be 100% compatible with a older versions. > > That then adds a wrinkle that we need may need to look at maintaining abi > dump archives per distro release, > or libabigail version depending on how you look at it.
This is something I had encountered. The Travis script flushes the ABI cache on a libabigail version change. When using the test-meson-builds.sh integration, the gen-abi.sh devtools script can be called to regenerate the dump files from the existing local binaries. > > An alter approach suggested by Dodi would be to just archive the binaries > somewhere instead, > and regenerate the dumps at build time. That _may_ be feasible, > but you lose some of the benefit (build time saving) compared to archiving > the abi dumps. > > The most sensible approach to archiving the binaries. > is to use DPDK release os packaging for this, installed to a fs sandbox. > > So the next steps are figuring out, which is the better option between > maintaining multiple abi dump archives, one per supported os distro. > or looking at what needs to happen with DPDK os packaging. > > So some work still to do here. I am still unconvinced about the approach, but I'll wait for your next proposal. -- David Marchand
