...
This build step provides a wrapper around the IncrediBuild "BuildConsole \Command" command line, geared for accelerating the build process of projects based on Make, MSBuild, WAF, ninja, scons, CMake or other build systems that are supported by default by IncrediBuild.
...
Step configuration requires setting the command to execute (e.g. make all).
Note that by default, IncrediBuild automatically adds a parallel processes switch (in Make, this switch is named -j; in MSBuild it is /m:). If a parallel processes switch is already part of the command line, IncrediBuild will change its value to a larger value in order to execute (and distribute) much more processes in parallel.
In MSBuild for example, IncrediBuild will change the value of an existing /m switch to a /m64, in the Make build system the -J flag will be changed to -j200. If the executed command is given in a Batch file (i.e. /command = Batchfile), and the MSBuild command that runs the build is inside the Batch file, IncrediBuild won’t be able to determine how to change the /m value, and therefore won’t change it. In this case, it is up to the user to replace or add a /m command with a high value to it (the recommendation is more than 40 for MSBuild and more than 100 to Make build system variants).
Optional Configurations
Optional BuildConsole parameters are grouped as; Distribution Control, Output and Logging and Miscellaneous.
...