Seems there's a few interesting tools out there to detect ABI breakage,
which might be useful for us in detecting if any of our 'patch' releases (1.3.x)
broke ABI wrt the parent minor release (1.3.0).
Of possible interest:
ABI Compliance Checker (ACC)
http://ispras.linuxbase.org/index.php/ABI_compliance_checker
GCC_XML
http://www.gccxml.org/HTML/Index.html
A comprehensive list of what C++ mods break ABI:
http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B#The_Do.27s_and_Don.27ts
The gcc one sounds interesting; it sounds like an extension to the
compiler itself to use its own internal data structures to detect
ABI breakage. I think the idea is it spits out an XML file for each
build, and if you compare the XML's between two builds, if they're
the same, the ABIs are the same.
_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
