JamPlus

The .vcproj and makefiles for wxWidgets use precompiled headers. You can accomplish the same thing by adding the following in a location before the Library line.

PrecompiledHeader core : ../../src/common/dummy.cpp wx/wxprec.h : $(SRCS) ;

In terms of output... because Jam is multithreaded, output from multiple processes gets interleaved. It can be hard to determine which process gave you which warning/error. JamPlus has a patch to collect the output from a process and display it all at once.

I share your frustration at lack of immediate output. I want to find a way to make this better. In the meantime, you can get more frequent output by splitting up the batch compilation command's size:

BatchCompileGroupSize core : 5 ;

This will batch just 5 files at a time to the compiler. On my machine, that makes the build of the core library a little over 2 seconds slower than batching them all to the compiler. It keeps the visuals more responsive, though.

Josh

Thanks for the explanations, adding the precompiled header made the build as fast or faster then visual studio, and the BatchCompileGroupSize showed more output. Thanks for your work in making jamplus possible!

Just found something interesting, if I create a visual studio workspace using the JamToWorkspace script, and build the project from within Visual Studio, I can remove the BatchCompileGroupSize rule and I still see the .cpp files being listed as they are built (although not JamPlus progress output). It almost seems like Visual Studio has some kind of way of being notified from cl.exe as files are built, although that's just a guess.

Just a note about this. JamPlus 0.4 has a new actions option, 'screenoutput', that will show output as it happens for the given action. This means one process's output will interleave with other multiprocess output, but the end result is more frequent visuals.

Josh