Ensured build environment is always compared with expected environment, whether or not it would abort the build because of it.

Changed building of tools targets so that it builds the targets listed in ${sf.spec.sbs.tools.config}, in sequence, rather than just buildng tools2_rel.whatlog followed by tools_rel.whatlog, regardless of the property.

Moved hlm:argSet definitions in sf-os-compile to be adjacent to the call that uses them. (And deleted three unused ones in the process.)

Update the PDK baseline for symbian2 builds

Updates to make the build environment check more reasonable: Mercurial v1.3 permitted The Java compiler is not a showstopping issue 7-zip can be installed in any location Update to Helium 5 Helium can be installed in PDT 1.*, not necessarily 1.0 Raptor installation path not significant Update to Raptor 2.9.* The Raptor patch to update the bundled version of python is no longer relevant BRAG calculations updated to ignore items not being in the system path, as this just doesn't matter. Overall effect is that the build environment check should pass on a machine that is able to do a build!

Regularised indentation

Fixed postAction in ats_specialise_test_drop.pl

Implemented FileStoreAction for BC tests

Implemented exporting Smoke Test Report to Diamonds

Updated postbuild to publish smoketest results

Updated ats_specialise_test_drop.pl to insert FileStoreAction param

Added new postAction to smoketest.xml

Restored signifcance of the MS tools not being available, as this only occurs when running a configuration that would try to use them.

Re-indented target "sf-os-compile" (following best guess as to the standard) to make it easier to read.