QA Matrix for Other Stuff

Cygwin GCC 3.4.4 bjam Debug

689 FB

Cygwin GCC 3.4.4 bjam Release

689 FB

Doxygen documentation Build

Win32 bjam Issues

Due to the bjam hackery involved in getting the manifest files to copy to their destinations while building with bjam, the debug/release variants must each be built with separate commands. i.e., the command:

bjam msvc-7.1 debug release

...will fail for debug, while

bjam msvc-7.1 debug
bjam msvc-7.1 release

...will succeed.

Mac OS bjam Issues

The 'install' stage of the bjam build process is hackneyed due to lack of an engineer fluent in bjamese. In some cases the copying of one or more file(s) will fail, in which case the destination file is then deleted successfully. A subsequent execution of bjam will then copy the file successfully to its final destination.

stderr Issues

Errors reported to stderr will go to the console on MacOS X; access to stderr is not easy on win32. An alternative should be explored.