Skip to main content
Last updated on Nov 05, 2024 IBConsole.exe, located in the Incredibuild installation folder, is a console application which initializes Incredibuild in various modes of operation, according to its various parameters. This chapter includes reference information on the command syntax and the available command parameters. IBConsole is intended for use in the Dev Tools package. In order to accelerate Visual Studio or other build tools that are part of the Make and Build Tools solution, use the BuildConsole command line interface.

​
Syntax

The basic command line syntax for running a job through the Automatic Interception Interface is:
*Other Options: Refer to the IBConsole Command Line Options section for the complete list of IBConsole command line options. Note: This command used to be called xgConsole, and that command is still supported.

​
Usage

The following syntax is used to operate IBConsole.exe:
OR
Where:
  • /COMMAND can specify any command line, for use in conjunction with the Submission Interface or Automatic Interception Interface.
  • <Target> can specify a path to an .xml/.xpx file defining the distributed Job (for use in conjunction with the XML Interface), or a path to a .bat file (for use in conjunction with the Submission Interface or Automatic Interception Interface)
Working with Dev tools requires you to use IBConsole, and use of IBConsole with Dev tools requires you to use one of the three interfaces that Incredibuild offers in order to connect between the software or script that you want to accelerate and Incredibuild. Note: If when running IBConsole you get the error message: “‘IBConsole’ is not recognized as an internal or external command, operable program or batch file.”, do one of the following:- Manually add the Incredibuild installation folder to your system path.- Rerun the Incredibuild setup application on your machine with the “Add Incredibuild folder to the system path” option selected.

​
Interface-Specific Usage and Examples

For examples and specific information regarding using IBConsole.exe to activate the different IB Interfaces, see the following sections: