VS Solution Settings
Note: This section is relevant for VS 2008 and earlier.
The Solution Settings dialog can be used to modify how IncrediBuild builds specific solutions and projects. This can be useful when specific behavior is only required when building with IncrediBuild, and also for performance and troubleshooting purposes. Options specified using the Solution Settings dialog are stored in an ".ib_ini" file, located in the same folder as the solution (.sln) or workspace (.dsw) file.
Accessing the Solution Settings Dialog
The Solution Settings dialog can be accessed using one of the following methods:
- The "IncrediBuild->Solution Settings" IDE menu command (VC7 and VC8 only).
- The Batch Build dialog "Solution Settings" button.
- The "IncrediBuild->Solution Settings" solution/project right-click context menu command (VC8 only).
The Solution Settings Dialog Layout
The Solution Settings dialog consists of two sections: In the left navigation pane, a tree-view allows you to choose where your modifications will apply – choosing the root solution/workspace will cause modifications to affect all projects in the solution/workspace, while changes made while a project is selected will only affect IncrediBuild builds of that project:
Solution Settings Dialog Pages
Select one of the following to learn more about the Solution Settings dialog:
Solution Settings Dialog - General Page
This page controls various project-level options that will only affect IncrediBuild builds:
Project OptionsBuild as an external projectProjects with this option selected are not built in a distributed mode, but are instead built as a whole by spawning a Visual Studio command line build process.Link OptionsIgnore "Do not create libraries" option (IncrediLink)Static library projects with this option selected always run the link step and create the .lib output file, regardless of whether the "Do not create libraries" option is currently enabled.This option only applies when IncrediLink is enabled. Link library dependencies (IncrediLink)For Visual Studio .NET (2002/2003) projects, this option can be used to specify whether output files from static library dependencies (sub-projects) will be linked into this project or not. For VS2005/2008/2010 projects, the "Link library dependencies" linker option (properties dialog) can be used to achieve the same result.This option only applies when IncrediLink is enabled. Ignore dependencies in Linker "Additional Options" sectionWhen this option is selected, modifications to files specified in the "Additional Options" field in the "Linker|Command line" properties page do not cause the project to re-link in incremental builds.Build PriorityProject Build PriorityProject priorities are used to indicate which projects should be built before or after other projects in a solution or workspace. IncrediBuild considers these indications when determining the order in which files and projects are built.IncrediBuild attempts to build files from "High" priority projects before "Normal" and "Low" priority projects, and files from "Normal" priority projects before "Low" priority projects. Dependency information still has precedence over project priorities, so a "High" priority file that depends on "Low" priority files is still built after its dependencies. Note:
Xbox Deployment OptionsRemote machine(s)The Remote machine(s) option can be used to specify IP addresses of bXbox/Xbox 360 machines that will be used in the deployment phase. Multiple semicolon-separated values may be entered. Solution Settings Dialog – Compiler/Linker PagesThis page allows removing and adding command line options to both linker and compiler steps. Settings made in this page only apply to IncrediBuild builds. To add and/or remove command line options to linker or compiler steps:
Notes:
Solution Settings Dialog – Edit & Continue PageThis page controls which files allow the Edit & Continue feature. Note:
Due to debug information format restrictions, IncrediBuild requires a predefined list of files that allow use of the Edit & Continue feature. These files cannot be compiled in parallel to other files and will only be built serially. Best practice for using Edit & Continue is:
Solution Settings Dialog – External Files PageThis page allows specification of files that will be compiled using standard VC compilation and will not be distributed (useful mostly for troubleshooting purposes).
|
Visual Studio Reference:
Batch Build Configurations
Accelerating Custom Build Steps, Build Events, and Build Tools
C# Acceleration
Using IncrediBuild for Visual Studio 2010 and Later
Further VS Build Performance Optimizations
Visual Studio 2008 and Earlier
IncrediBuild Solutions:
Visual Studio Solution
Make and Other Build Tools Solution
DevTools Solution
IncrediBuild for Qt Creator
IncrediBuild For Game Development
IncrediBuild for Unit Tests
Working with Build Groups
Running Gitlab Builds with Incredibuild
User Manual:
List of Open Sources
Getting Started
Set Up and Installation
IncrediBuild Solutions
The Coordinator
IncrediBuild Agents
IncrediBuild Cloud
Working from Home
Troubleshooting Issues
IncrediBuild Additional Resources
Release Notes