On mercredi 26 octobre 2016 23:54:33 CET Albert Astals Cid wrote:
> 2) Make it a manual step (sorry David), we could have a script that for
> every release downloads and compiles the tarballs of it and the previous
> version and runs abidiff on them.
>
>
> Currently I am kind of leaning towards 2
El dijous, 27 d’octubre de 2016, a les 9:20:29 CEST, Jaroslaw Staniek va
escriure:
> On 26 October 2016 at 23:54, Albert Astals Cid wrote:
> > Does anyone have other ideas or thoughts on it?
>
> Three things:
> - the Qt project has own solution for the checks, maybe worth looking
> - try to con
On 26 October 2016 at 23:54, Albert Astals Cid wrote:
>
>
>
> Does anyone have other ideas or thoughts on it?
>
>
Three things:
- the Qt project has own solution for the checks, maybe worth looking
- try to convert the compiler-specific decorated symbols to some uniform
notation and compare just
Hello Albert,
On Wed, Oct 26, 2016 at 11:54:33PM +0200, Albert Astals Cid wrote:
> 1) Have a helper repository where we upload the XML files of the ABIs exactly
> produced by the CI nodes and then make CI check against that on every build.
>
> This still has some issues on how we actually fill t
Hi there, one of the things we say we maintain but we don't really have
autotests for is maintaining ABI compatibility.
I recently learnt about abigail, a tool that for checking ABI compatibility.
Basically we are interested in two tools abidw and abidiff
abidw creates an XML file with the ELF
