Skip to main content
Last updated on Dec 25, 2025 The /command switch enables the Make and Build Tools capability of the BuildConsole command line interface. This capability highly accelerates the build time of various build tools applications (e.g., Make and Ant), by distributing build tasks that are to be executed in parallel to remote machines across the network, utilizing their idle CPUs. Only one build at a time can be executed on a single initiating machine. An attempt to run a build while another is running, pauses the build until the currently running build ends. Only then, does the new build begin to run. To accelerate your build time, ensure that the build tools are installed on the initiating machine and then run: BuildConsole /command="<your original build command line>" [Options] For example: BuildConsole /command="make --file=makefile.mak -B" By default, Incredibuild automatically adds a parallel processes switch (in Make -j; in msbuild /m:).
  • If Make is executed directly, Incredibuild changes the value of an existing -j switch to 1024 (by default). Add the /keeporigjobsnum if you want to keep your -j switch value.
  • If Make is executed from a Batch file, that is, /command = Batchfile, Incredibuild does not change the -j value.
  • If <your original build command line> contains the -j switch (as used, for example, with Jom builds), it is recommended to define a high -j value, no fewer than the maximum number of cores.
Incredibuild changes the following switches:
Note: If when running BuildConsole /command, you get the error: BuildConsole is not recognized as an internal or external command, operable program or batch file., either manually add the Incredibuild installation folder to your system path, or rerun the Incredibuild setup application on your machine, making sure that the Add Incredibuild folder to the system path option is selected.

Command Line Options

Return Codes

BuildConsole returns the following return codes:
  • 0 – Build succeeded with no errors
  • 1 – Build failed due to error not related to Incredibuild (e.g. compilation error)
  • 2 – Build cancelled by user request
  • 3 – Build failed due to Incredibuild system error

Make, Jom and NMAKE Samples

There are three pre-built sample projects demonstrating how to use Incredibuild in the Samples\Make And Build Tools folder under the Incredibuild installation. To run the samples:
  1. Define the location of the Make/Jom/NMAKE executable in the path, to allow for initiation from any folder.
  2. Run the RunMakeSample.bat/RunJomSample.bat/RunNmakeSample.bat from the command prompt.
  3. The examples are configured to use the MS Visual Studio 2010 compiler. If you have a different Visual Studio version installed, open the bat files and replace call “%VS100COMNTOOLS%vsvars32.bat” with:
    • MS Visual Studio 8.0: call “%VS90COMNTOOLS%vsvars32.bat”
    • MS Visual Studio 7.0: call “C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat (change the Visual Studio installation folder if required)