Hi Andrey, Il 06/03/2014 18:00, Andrey Ponomarenko ha scritto:
I think, it's better to create a single report in order to avoid duplicated data in your reports. For example, the QtConcurrent and QtCore header files recursively include intersected sets of symbols and therefore corresponding reports show the same changes.Example of alternative single report in the API tracker: http://upstream-tracker.org/compat_reports/qt/5.2.1_to_5.3.0-alpha/abi_compat_report.html To produce such report just list all headers in the <headers> option of the input descriptor to the abi-compliance-checker tool.
Thanks for the tip.I was trying to get per-module reports so that the respective maintainers could take a look at the issues, but indeed it seems impossible to get abicc not to complain about cross-dependencies. But I guess we could just run abicc on the entire set of Qt modules which are promising ABI compatibility.
Thanks, -- Join us Oct 6-8 at BCC Berlin for Qt Developer Days 2014! Giuseppe D'Angelo | [email protected] | Software Engineer KDAB (UK) Ltd., a KDAB Group company Tel. UK +44-1738-450410, Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions
smime.p7s
Description: Firma crittografica S/MIME
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
