[
https://issues.apache.org/jira/browse/STDCXX-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591321#action_12591321
]
Martin Sebor commented on STDCXX-731:
-------------------------------------
One relatively easy, semi-automatic way of doing this would be to enhance the
[{{buildntest}}|http://svn.apache.org/repos/asf/stdcxx/trunk/bin/buildntest]
script to do two builds with two sets of sources, then swap the libraries, and
rerun all examples and tests. The results of those builds would then be
processed by the
[{{xbuildgen}}|http://svn.apache.org/repos/asf/stdcxx/trunk/bin/xbuildgen]
script to produce a single cross-build report.
> framework to verify binary compatibility
> ----------------------------------------
>
> Key: STDCXX-731
> URL: https://issues.apache.org/jira/browse/STDCXX-731
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Test Harness
> Affects Versions: 4.2.0
> Reporter: Martin Sebor
> Fix For: 4.2.2
>
> Original Estimate: 80h
> Remaining Estimate: 80h
>
> In the 4.2.0 release we ran into binary incompatibilities late in the release
> cycle that ended up costly to fix. What would have prevented the
> incompatibilities, or at least allowed us to detect them early on, would have
> been an automated framework to verify the binary compatibility of the
> library. This is a placeholder issue to design and implement such a framework.
> I'm guesstimating the effort of putting something like this in place at 80
> hours, possibly more.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
