Add rtems-bsp-builder.

This is a testing tool that builds BSPs with a range of configure options
for regression testing changes do not break the kernel code.

The builds are controlled by an INI file. The INI configuration has profiles
which define a specific set of architures and BSP to build. There are architectures
which contain BSPs and these further define the options needed to build the BSP.
There is also builds which define the variations each BSP is built with.

The build output can be pointed to any suitable disks so you can control where
the output ends up.

This initial release contains tiers and these are only seeded with something to
test with. It does not define the tiers.

Wanrings, object files and libraries are counted.

1 files changed, 134 insertions, 0 deletions

diff --git a/tester/rtems/rtems-bsps.ini b/tester/rtems/rtems-bsps.ini
new file mode 100644
index 0000000..f196988
--- /dev/null
+++ b/tester/rtems/rtems-bsps.ini
@@ -0,0 +1,134 @@
+#
+# RTEMS Tools Project (http://www.rtems.org/)
+# Copyright 2016 Chris Johns (chrisj@rtems.org)
+# All rights reserved.
+#
+# This file is part of the RTEMS Tools package in 'rtems-bdp-builder'.
+#
+# Permission to use, copy, modify, and/or distribute this software for any
+# purpose with or without fee is hereby granted, provided that the above
+# copyright notice and this permission notice appear in all copies.
+#
+# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+[profiles]
+profiles = tier-1, tier-2, tier-3, tier-4
+
+#
+# Tier 1: no build errors and no unexpected tests failures on hardware.
+#
+[tier-1]
+archs      = arm, i386, sparc
+bsps_arm   = xilinx_zynq_zc706
+bsps_i386  = pc686
+bsps_sparc = erc32
+
+#
+# Tier 2: no build errors and no unexpected tests failures on hardware and
+#         simulators.
+#
+[tier-2]
+archs      = arm, sparc
+bsps_arm   = xilinx_zynq_a9_qemu
+bsps_sparc = sis
+
+#
+# Tier 3: no build errors, no tests run.
+#
+[tier-3]
+archs      = arm, moxie
+bsps_arm   = lpc1768_mbed
+bsps_moxie = moxiesim
+
+#
+# Tier 4: nothing expected.
+#
+[tier-4]
+archs = epiphany
+bsps_epiphany = epiphany_sim
+
+#
+# Architectures
+#
+[arm]
+bsps = xilinx_zynq_a9_qemu, xilinx_zynq_zc706
+
+[i386]
+bsps = pc686
+excludes = smp
+bspopts_pc686 = BSP_PRINT_EXCEPTION_CONTEXT=1
+
+[sparc]
+bsps = erc32, sis
+
+[powerpc]
+bsps =
+
+[epiphany]
+bsps = epiphany-sim
+
+#
+# The Build Options define how each combination is to be build.
+#
+[builds]
+#
+# The variations, default is Yes and can be overriden in an architecture.
+#
+variations = debug, profiling, smp,
+	     posix, no-posix, posix-debug, posix-profiling, posix-smp,
+	     network, no-network, network-debug, smp-network, smp-network-debug
+#
+# The default build, tests the default configuration, all variations are added
+# on.
+#
+default = --target=@ARCH@-rtems@RTEMS_VERSION@
+          --enable-rtemsbsp=@BSP@
+          --prefix=@PREFIX@
+          --enable-tests
+#
+# The options for each varations.
+#
+debug             = --enable-debug
+profiling         = --enable-profiling
+smp               = --enable-smp
+posix             = --enable-posix
+no-posix          = --disable-posix
+posix-debug       = --enable-posix --enable-debug
+posix-profiling   = --enable-posix --enable-profiling
+posix-smp         = --enable-posix --enable-smp
+network           = --enable-networking
+no-network        = --disable-networking
+network-debug     = --enable-debug, --enable-networking
+smp-network       = --enable-smp --enable-networking
+smp-network-debug = --enable-smp --enable-debug --enable-networking
+
+#
+# Define how each profile is to be treated. Note, hardware vs simulator testing
+# is handled in the configuration, there is not specific test to determine
+# this.
+#
+[tier-1-profile]
+active = Yes
+build = Yes
+tests = Yes
+
+[tier-2-profile]
+active = Yes
+build = Yes
+tests = Yes
+
+[tier-3-profile]
+active = Yes
+build = Yes
+tests = No
+
+[tier-4-profile]
+active = No
+build = No
+tests = No