From: Ponomarenko A. <and...@ya...> - 2015-11-20 21:09:05
|
29.10.2015, 19:59, "Tom Hacohen" <to...@os...>: > On 19/10/15 20:52, Ponomarenko Andrey wrote: >> Hello, >> >> I noticed that you maintain binary compatibility of the EFL and Elementary here: https://devs.enlightenment.org/~tasn/abi/ >> >> Recently I've started to maintain it too on my personal web-page: http://abi-laboratory.pro/tracker/timeline/efl/ >> >> The source code of the ABI tracker is open and you can set up it locally on your site along with the old tracker. It's also based on the abi-compliance-checker tool, but doesn't require compilation of header files. It uses DWARF debug info from shared objects instead. > > Hey, > > Thanks for sharing, and good to have another report. Especially as > concise as nice looking as yours. > > While it's good to not have to compile the header files, not compiling > them doesn't really tell the whole story. Changes in macros (which we > have and do), don't show. Same goes for changes in struct, enum and > value definitions. Checking the headers is essential. > > The abi-compliance-checker tool actually shows both the info from the > objects ("Binary compatibility") and from the headers ("Source > compatibility"). There's a slight overlap between the two, but there are > things that show in one and not the other. > Yes, the new approach doesn't allow to check macros, but it checks structs, enums and other data types properly. The tool takes definitions of data types from objects debug info instead of header files. See for example: http://abi-laboratory.pro/tracker/compat_report/efl/1.15.2/1.16.0/ebf11/abi_compat_report.html#Type_Problems_Low Thank you. |