Archived
This forum has been archived. Please start a new discussion on GitHub.
Provide stable ABI
Hi,
I've recently added Ice to our ABI tracker:
Test results and ABI changes analysis for the library Ice on x86
It has detected an ABI break between 3.4.0 and 3.4.1:
ABI compliance report for the library Ice from version 3.4.0 to 3.4.1 on x86
Is it an unintentional break? If so, you can use abi-compliance-checker tool to prevent such breaks in future releases.
I've recently added Ice to our ABI tracker:
Test results and ABI changes analysis for the library Ice on x86
It has detected an ABI break between 3.4.0 and 3.4.1:
ABI compliance report for the library Ice from version 3.4.0 to 3.4.1 on x86
Is it an unintentional break? If so, you can use abi-compliance-checker tool to prevent such breaks in future releases.
0
Comments
-
Hi,
Thanks for the suggestion. The tool is reporting changes in the Slice namespace. The functions and classes from this namespace are internal and used by the Slice compilers, we in general don't maintain binary compatibility for this shared library (you have to use the same libSlice version as the slice compiler version). It also reports a removed Glacier2::Application::router() static method. However, it's still there so this one looks like a false positive.
Cheers,
Benoit.0