Hi Giuseppe, 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. Giuseppe D'Angelo wrote: > From 5.2.2 (release branch) to 5.3.0 alpha, Linux x86-64, GCC 4.6, > debug build. > > Could it be possible to add abicc reports to some kind of nightly > runs, like the ones used to do documentation snapshots? > >> http://www.kdab.com/~peppe/qt/compat_reports/QtConcurrent/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtCore/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtDBus/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtGui/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtNetwork/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtOpenGL/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtPrintSupport/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtTest/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtWidgets/5.2.2_to_5.3.0/compat_report.html >> >> >> http://www.kdab.com/~peppe/qt/compat_reports/QtXml/5.2.2_to_5.3.0/compat_report.html >> >> -- Andrey Ponomarenko, NTC IT ROSA. _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
