RSS Feed
Knowledgebase : Usage
In some processes, it may be necessary for the same output file to be written to several times, from different Agents. A typical example is a log file which gets incrementally updated by the different running tasks. With IncrediBuild, such access might ...
Adding a preprocessor definition from cl command line is possible by adding the "/cl_add" option to your build command in the following way: /cl_add="/D DEFNAME=VALUE" This actually adds the specified parameter to the cl command line when executed. /D s...
The AllowRemoteIf and DenyRemoteIf XML Profile parameters allow you to control the way tasks are distributed.  Therefore, the parameter of these should be some unique part of the task command.    ALLOWREMOTEIF EXAMPLE:   
if the process reports an error by writing to the command console's output - IncrediBuild can recover it.  IN ORDER TO SET THIS SAFEGUARD, PLEASE ADD THE FOLLOWING VALUES TO THE REGISTRY:  * HKEY_LOCAL_MACHINESOFTWAREWow6432NodeXoreaxIncrediBuildBuil...
Sometimes a custom build step, build event or a build tool can be further broken down to smaller tasks, and parallelized to achieve further acceleration. This method can be used in Visual Studio versions 2010 and higher, and allows the distribution and ...
IncrediBuild supports Visual Studio Express 2010 - 2013 However, the integration of IncrediBuild with Visual Studio Express is slightly different than its integration with the regular Visual Studio development environment. The reason for this difference...
IncrediBuild can run in parallel the linking steps and distribute custom steps / build events. However, the linking steps parallel execution is bound only to the Initiator machine so those steps cant be distributed to remote machines. Custom steps defau...
CMD has a limit of 8192 characters.  Longer command line arguments require a script file to execute the command.
NOTE: A valid DevTools Solution license is required to use XML Profiles when using IncrediBuild. Sometimes there is a need to define specific exit codes since certain programs don't always return 0 as a success code and 1 as a failure code.  FOR VISU...
Currently, there is no setting to disable Predicted Execution for specific projects, but there is a workaround.   Predicted Execution will automatically be disabled for projects where you have specified a custom step. This happens because IncrediBuild d...
It is possible to disable specific Build System warnings using the Agent Settings dialog "Build Monitor->Warnings" page.
The following technique can be used in order to accelerate Microsoft nmake builds using IncrediBuild: 1. copy cl.bat and link.bat from the "SamplesMake And Build ToolsNmake" folder under the IncrediBuild installation folder to either the project folder ...
Scons and many other Make tools [http://www.incredibuild.com/webhelp/webframe.htm#IB_for_Make_and_Build_Tools1.html] are supported by default with IncrediBuild In order to run a Scons build, all you need to do is to run the following command: buildconso...
There are two types of makefile projects: 1. Visual Studio projects of the "makefile" project type. These are basically a collection of command lines: one for the Build operation, one for Rebuild and one for Clean. IncrediBuild builds these projects exa...
The "Use Library Dependency Inputs" is a linker option introduced in Visual Studio 2005 (Project properties dialog, under "Linker|General") that basically does the same job IncrediLink does (linking in .obj files instead of static .lib files, to speed up ...
Running distributed Fortran builds through the IncrediBuild XGE Interfaces extension package is possible but requires a bit of work: For each source file, define a custom step that runs the exact command line for that file (calling the Fortran compile...
Presets created in the Batch Build dialog are stored in an ".ib_preset" file, located in the .sln file's folder. Simply copy this file along with the .sln file to distribute presets across machines.
Overview: Incredibuild can accelerate Ninja builds in 2 ways: * Running the ninja builds from Visual Studio IDE or command line as part of Visual Studio build. * Running the ninja build directly from the command line using the ninja build command. ...
In order to mark a project to run locally right click the project in Visual Studio, go to "Properties"->"Configuration Properties"->"C/C++"->"Preprocessor Definitions" and add the string -   "IB_RunLocal"  For VS2008 and below, use "Solution Settings"...
The Build Monitor Output Display allows viewing the output created by a task initiated through the Visual Studio IDE, BuildConsole or IBConsole. When a task is created through the Visual Studio IDE or BuildConsole, all errors and warnings created during ...
For each build, IncrediBuild creates a temp subfolder under TMP with its own special temp files.  If there are two builds, one may generate a certain output that will be kept in the 1st subfolder and the 2nd build may need to use these files to successf...
The following three methods are easy ways to check if IncrediBuild is currently building on your machine * When IncrediBuild is running the following registry key is set to the following value:  XoreaxBuildContext=1  * If the machine you are using i...
Sometimes it is useful to assign names to different groups of Agents in your build farm, so you can later sort the Coordinator display by group attribution. The Build Groups feature isn't suitable for this job since it creates individual build groups that...
The following instructions valid for Visual Studio .NET / 2005 / 2008 and explain how to specify a file that will be compiled using the standard compiler, in non-distributed mode. This can be useful if IncrediBuild consistently fails to compile a specif...
It is possible to have several builds running using one Coordinator, However only one job can be started on each Agent. It is, however, possible to 'queue' several builds for execution on one Agent. This can be done by starting the build from the comm...
Description: While an Agent is disconnected from the Coordinator, it might not utilize all the local cores even if the Agent's license includes the relevant license core package. Workaround: (assuming license supports the cores amount on the local machi...
Starting from v4.0 (and later), IncrediBuild supports precompiled headers in a variety of compilers including gcc and gcc variants. In order to enable this support in IncrediBuild's Automatic Interception Interface build, a new property "AutoReserveMem...
Yes, it is possible for a job/tool to query which Helper Agent it's running on by using the 'xgHelperID' environment variable. The 'xgHelperID' environment variable (available from version 3.11 and on) returns a number uniquely identifying the Helper CP...
Following is an overview of the Coordinator/Agent communication protocol and TCP/IP ports: The Agent service (BuildService.exe) on each Agent machine connects to the Coordinator service (CoordService.exe) on initialization, and continuously does so dur...
Visual Studio 2010 and newer versions use the MSBuild engine which executes all custom build tools and custom build rules within the context of a single project in a sequential  manner – on a single CPU core For example, in the following scenario: A cus...
It is possible to filter which files will be returned to the Initiator machine.   TO DO SO, DO THE FOLLOWING:  * On the Coordinator machine, right click on theIncrediBuildtray icon and open the Coordinator Monitor  * On the Coordinator Monitor , y...
This article shows how to build specific projects on the local machine, without using IncrediBuild's build action. Please note this this setting can be used only with VS2005 / VS2008 This can be helpful as a workaround for projects that fail to build wi...
  ISSUE:  The build progress screen shows "csc" processes for source files which are not a part of the build - such as: "bi5cu1dy", "ixgwolfz", "pvcmod5x"…  Furthermore, the "csc" process cannot be found in the Output screen of build monitor.    ...
In some builds the tasks that are being executed on the Helper machines produce special output files which are needed on the Initiator machine. In some cases, those special files are not being synchronized back to the Initiator by default. It is possib...
Due to debug information format restrictions, IncrediBuild requires a predefined list of files that will allow use of the Edit & Continue feature. These files cannot be compiled in parallel to other files and will only be built serially on the local machi...
The cl_IncrediBuild_Interop*.exe files are copies of the compiler generated by IncrediBuild when Interoperability mode is enabled. interoperability mode is enabled to allow mixing of intermediate files generated by IncrediBuild with files generated by Vis...
The Agent file cache contains the following types of files: - Source files (.cpp, .h, etc.) - "External" source files such as system include files. - PCH files - remote copies of compiler executables * Duplicates are stored only once and are do n...
To achieve distribution, IncrediBuild compilations produce multiple PDB files in the project's intermediate folder, while VC compilations only create one file (typically "vc80.pdb" or "vc70.pdb"). When the project is linked, debug information from all ...
Help Desk Software by Kayako xoreax.helpserve.com