Tue, 06 Apr 2010 21:24:03 +0100 Extend the summarise_rvct4_errors.pl script so that it picks up linker errors
William Roberts <williamr@symbian.org> [Tue, 06 Apr 2010 21:24:03 +0100] rev 4
Extend the summarise_rvct4_errors.pl script so that it picks up linker errors Also make it possible to scan the raptor Makefile.xxxx.log with this tool, for checking builds
Wed, 31 Mar 2010 11:44:26 +0100 Update gcce summary tool to note the affected packages, and update summary text
William Roberts <williamr@symbian.org> [Wed, 31 Mar 2010 11:44:26 +0100] rev 3
Update gcce summary tool to note the affected packages, and update summary text Add basic RVCT summary tool and corresponding summary.
Fri, 26 Mar 2010 16:26:39 +0000 Update the summary based on the latest gcce CompilerCompatibility package builds as at 2010-03-26
William Roberts <williamr@symbian.org> [Fri, 26 Mar 2010 16:26:39 +0000] rev 2
Update the summary based on the latest gcce CompilerCompatibility package builds as at 2010-03-26
Fri, 26 Mar 2010 16:25:15 +0000 Add script to summarise GCC errors (and warnings) from the "*_failures.html" logs
William Roberts <williamr@symbian.org> [Fri, 26 Mar 2010 16:25:15 +0000] rev 1
Add script to summarise GCC errors (and warnings) from the "*_failures.html" logs Add script to grab the various *_failures.html files based on the HTML page for a "list of gcce package builds" Add the result of applying the summarising script to the original gcce platform build
Mon, 22 Mar 2010 21:41:09 +0000 Created the examples directory, containing components called "before" and "after"
William Roberts <williamr@symbian.org> [Mon, 22 Mar 2010 21:41:09 +0000] rev 0
Created the examples directory, containing components called "before" and "after" The before directory is a component which illustrates typical issues that GCC has with the Symbian source code. Compiling this component (sbs -b bld.inf -k -c armv5_udeb_gcce4_4_1) will produce multiple errors, hence the use of "-k" to keep going. The after directory is the same component with fixes applied - compiling in the after directory should produce no errors. The aim is to keep the code very closely aligned to the before component, so that they can be compared with visual diff tools such as Beyond Compare. Sometimes it's valuable to be able to compile this code with the default production compiler, (currently RVCT 2.2) so the MMP files will switch the name of the generated executable if a different compiler is used.
(0) tip