Refactor the reporter to allow the setbuilder to use its build config
rather than regenerating the configuration from the configuration file.
Using the config file and the build macros exposed an issue if a
macro was undefined that was defined in a build set above the
config file. Using the build set's configuration as used to build
is a better solution.
The reporter was refactored to allow a config class to be used
to report.
The setbuild can now take a configuration file as an input file.
A build could require more than one map to be active at once. This
change allows more than one map to be set. An example is gcc and
newlib. Having separate maps allows a user to control which part
they test.
Add support to use a git cloned repo as the source. Move the download
code out of the build module and into a separate module. Add to this
module support for git.
Update the GCC common configuration to support using a symlinked
git repo.
Add checks for all languages.
This is used in the configuration scripts to specify which
libraries you want to be linked as static. For gdb this is
libexpat which is built as part of most build sets.
Added a check in the options post processing to check is the
prefix path allows writes. No actual write check is made. just
the permissions are checked. If the --no-install options is
used the check is not made.
Moved the --no-install option from the set builder to the options
module.
User macro files passed on the command line allow a user to
override the defaults in configuration files to test new changes
in pending releases.
Fix macros issues with keys with more than one map.
Package descritions and info and now always added to macros.
Hack to get the source in macros into the source this. This needs
to move to the package class and will soon.
Fix a bug where the old defines was still referenced.