to explicitly use string::iterator. Wave builds
shared and runs on both Darwin and Linux, I'm
not wave conversant so it does startup but I
don't know what to do next.
Wave: A Standard conformant C++ preprocessor based on the Boost.Wave library
Version: 2.3.2.4432 [linux/GNU C++ version 4.4.6 20120305 (Red Hat 4.4.6-4)]
(20120523)
I replaced an auto declaration that was preventing
cross-platform building of compile_status.cpp. I'm
now able to run b2 in boostorg/tools and have everything
buid.
Since results reporting limits output to 64kb we'll
do the same with target output collected by bjam.
This should help clang testers with develop branch.
Strangely enough git submodule command allows you to pass
the --init argument to submodule update.
git submodule update --init
We can eliminate one extraneous call to git, should slightly
help regression testers.
The problem can be reproduced in a clean regression
test directory by first running tests with --tag=master
and then running tests with --tag=develop. The fix,
as Beman pointed out, is to init the submodules.
Fortunately the init command is a noop for existing
submodules so added this command to the git testing
sequence when the boost_root directory already exists.
With this patch applied, I am now able to run tests
with master first, and develop second, no error. Tested
on Linux and Darwin.
directory more than once, and the --tag differs. If
the boost_root directory already exists, add a new
remote for a different branch (remote set-branches)
and added an explicit checkout on this branch.
If you run run.py script once with --tag=master,
and again with --tag=develop, the script will now
correctly checkout develop the second time and
will run tests using the develop fork rather than
master.
