If the CONF_XML environment variable is set, use that conf.xml file instead of the standard $PAPARAZZI_HOME/conf/conf.xml
Meaning you can run tests for a different conf without changing the conf.xml symlink, e.g.
```
CONF_XML=$PAPARAZZI_HOME/conf/conf_tests.xml prove tests/examples
```
using [libtap](https://github.com/zorgnax/libtap) to create a [TAP](http://testanything.org) (TestAnythingProtocol) producer.
You can also run the test (if already compiled) with prove:
```
prove --exec '' tests/math/test_pprz_math.run
```
Examples on how to test compile all aircrafts/targets in your current conf.xml:
with parallel compilation and showing full output during compilation
$ J=AUTO prove tests/examples -v
only showing full compile output if there has been an error, if there were warnings only print those
$ SHOW_WARNINGS_ONLY=1 prove test/examples
with parallel compilation and treating all warnings as errors:
$ J=AUTO USER_CFLAGS=-Werror prove tests/examples
Also replace LOCAL_CFLAGS (which wasn't used anymore) with USER_CFLAGS (and add where missing).
Now you can e.g. test compile all aircrafts/targets in your conf and add extra flags like treating warnings as errors:
$ J=AUTO USER_CFLAGS=-Werror prove conf/examples
Check exit status instead of whether output contains the word Error.
With ForceArray on xmlSimple no need to check for target separately.
Also don't filter on list of firmwares, build all..
make AIRCRAFT=BOOZ2 clean_ac nps.compile
make AIRCRAFT=LisaLv11_Aspirinv15_Overo_RC clean_ac nps.compile
make AIRCRAFT=LisaLv11_Booz2v12_RC clean_ac nps.compile
make AIRCRAFT=Quad_LisaM_2 clean_ac nps.compile
Adding more support modules that are needed by XML::Simple to read the
conf/conf.xml.example.
Adding these files into the repository means that users don't need to
install them on their computers.
Adding the XML::Simple perl module into the tests/lib directory so that
normal users don't need to install it to run the tests.
Reformatted the conf/conf.xml.example file to not all be on single
lines for each config since this is now not required as we're parsing
the XML.
The JUnit results can be added by specifying JUNIT=1 from the make
command line.
This is important as the Bamboo server can read JUnit results and
include them in the build reports.
This requires that the Perl module TAP::Formatter::JUnit is installed
on the host that the command is run on.
The JUnit results are created under tests/results and have the name
ABC.junit.xml
Felix Ruess
Gautier Hattenberger
Bernard Davison