<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thank you for your useful feedback.<br>
We have corrected all problems you specified and have released beta3
version.<br>
<br>
As we can see you have a lot of header files to check (1939), so you
can specify -fast option for acceleration of checking process (in this
case you must specify library descriptor more completely for avoiding
compilation errors).<br>
<br>
Andrey Ponomarenko.<br>
<br>
Thiago Macieira wrote:
<blockquote cite="mid:200907290931.54190.thiago@kde.org" type="cite">
<pre wrap="">Andrey Ponomarenko wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Colleagues, I'm a lead developer from Institute for System
Programing of Russian Academy of Sciences and we are developing a free
lightweight tool for checking backward/forward binary compatibility of
shared C/C++ libraries in OS Linux. It checks interface signatures and
data type definitions in two library versions (headers and shared
objects) and searches differences that may lead to incompatibility
according to ABI standards. We have released beta version of this tool
and we'd like you to consider its usefulness for your project.
The package with the latest version of tool is in the attachment.
The wiki-page of binary compatibility checker is
<a class="moz-txt-link-freetext" href="http://ispras.linux-foundation.org/index.php/ABI_compliance_checker">http://ispras.linux-foundation.org/index.php/ABI_compliance_checker</a>
</pre>
</blockquote>
<pre wrap=""><!---->
Hello Andrey
I've tried the tool. Here are some initial reactions:
1) please align your XML-like structure properly. It looks sloppy.
2) the descriptor template is missing a / in the last section.
3) please add some output to abi-compliance-checker.pl -d; it took me
quite a while, reading the code, to find out it had created a file called
descriptor.txt
4) I made a typo in the gcc_options section and, when I ran the tool, I
got this:
$ /tmp/abi-compliance-checker-1.0.0-beta2/abi-compliance-checker.pl -l Qt
-d1 qt4.6 -d2 ../qt-4.5/qt4.5
preparation...
checked headers: 0/1939 (0%) mv: cannot stat `Qt1.h*.tu': No such file or
directory
ERROR: can't create gcc dump
After reading the source code, I found out about the header_compile_errors
subdir, where there was a message from gcc saying "gcc: unknown option -
fvisibility-inline-hidden". But the tool didn't help me. It was just a
cryptic error message.
5) in your wiki, you have KDE TechBase, “Policies/Binary Compatibility
Issues With C++” as a reference, but the link points to the old document.
Please update it to
<a class="moz-txt-link-freetext" href="http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++">http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++</a>
I've now got the tool to run. I'll let you know what the results are.
</pre>
</blockquote>
<br>
</body>
</html>