this can be very useful when debugging unit test problems as when run outside waf then the LD_LIBRARY_PATH (or PYTHONPATH if used with pytest extra) is set dynamically by waf and therefore running the executable manually or via gdb is not immediate
all the environment will be dumped in python script that can then be executed to run manually tests.
* cppcheck: fix extra forn multiple build rules are in a single wscript
When executed the output from cppcheck will be put inside cppcheck.xml and
then the generated error output inside cppcheck/index.html (and related
subfiles). Of course if two separate build rules are present the files
will clash with each other and data will be lost.
So this will not work in previous version:
bld.program(source=bld.path.ant_glob('src/ex-prog-*.cpp'), includes='src/', target='ex-prog-c')
bld.program(source=bld.path.ant_glob('src/ex-prog2-*.cpp'), includes='src/', target='ex-prog2-c')
In the output just one of the two results will be there (or in worst case
we will have files being deleted/garbled) as they both try to work on
cppcheck.xml and index.html (in build and build/cppcheck respectively)
With this commit the xml/html files have a reference to the task name (so
appended with a dash) so they are unique and don't clash. Also all the
messages to the user are corrected accordingly so the user is pointed to
the correct name of the file (and so are the internal links generated in
the html file).
In the previous case we will have:
ccpcheck detected (possible) problem(s) in task 'ex-prog2-c', see report for details:
file:///home/fede/waf/cppc/build/cppcheck/index-ex-prog2-c.html
ccpcheck detected (possible) problem(s) in task 'ex-prog-c', see report for details:
file:///home/fede/waf/cppc/build/cppcheck/index-ex-prog-c.html
* cppcheck: Provide as an option also old way of single index.html file for compatibility
Sometimes it is useful to be able to add a module to waf as a tool.
Using this patch one can use ./waf-light configure build --tools /tmp/mytool
This will add the files under /tmp/mytool under /waflib/extras/mytool. Such
that they can be imported in a wscript as from waflib.extras import mytool.
If compiler_cxx was not configured before qt5 then qt5 will try to build applications with an empty compiler which gives very strange errors in the config log
