Explicitly flushed bjam's standard output after printing out '...patience...' lines. Without a fflush() call these lines may get buffered and displayed all at once only after the first actual target has been built. It seems that Visual C++ compiler's runtime does not use line buffering for its standard output stream if given a pipe as its standard output (encountered with bjam compiled using msvc 10 and run by piping its output through the Cygwin tee utility).
(No files)
Note:
See TracChangeset
for help on using the changeset viewer.