|
DistributionRestart remote processes on local machine when possibleThis option (enabled by default) helps prevent cases in which a job "waits" for a slow remote machine to complete execution of a task. If this scenario is reached when this mode is enabled, IncrediBuild will execute this task on the local machine in parallel to the remote machine, and output from the first machine to complete the task will be applied to the build.Note that when this mode is enabled, you may see two execution bars of the same target running at the same time; when one of the bars completes, the other bar will disappear signaling that the faster machine's output was applied to the build. Avoid task execution on local machine when possibleWhen this option is enabled, tasks that may be remotely executed (C/C++ compilation, MIDL, etc.) will run only on remote machines and the local machine will be used exclusively for tasks that can only be executed locally (linking, for example). Note that when this option is disabled, local execution of distributable tasks will be avoided if the local system's resource becomes very busy.Enable Standalone ModeEnables a mode in which the Agent uses only its local CPUs when it initiates builds. The Agent will still participate in remote builds initiated by other Agents.Build Completion Sound3 options are available:Disabled - Build completion sound is disabled. System Beep - A system beep is sounded when a build completes. Use Control Panel sounds - IncrediBuild will use user-specified sounds for each of the following events: successful build completion, build failure and build cancel. To modify build sound settings, use the "Sounds and Audio Devices" Control Panel utility. |
| Converted from CHM to HTML with chm2web Standard 2.85 (unicode) |