Terminology¶
Terms specific to the Turbo Build Accelerator¶
Build¶
The initiated build of a Visual Studio Solution (of multiple Projects) or a single Visual Studio Project.
Build Session¶
A Build Session is the collection of c/c++ compilations required within a Visual Studio Project.
Note that msbuild.exe controls what is contained within a Build Session since a large project may be split into multiple invocations of the Hook process.
Build Job¶
A Build Session comprises of several Build Jobs. Each one of these equates to a c/c++ source file.
Build Job Item¶
A Build Job comprises of several Build Job Items. Each one of these equates to a step within the build of a c/c++ source file.
Typically there will be the following steps : - preparation step (pre-processing) - compilation step
Build Queue¶
The list of Build Jobs within the Agent.
Scheduling Queue¶
The list of Build Jobs within the Scheduler.
Cache¶
The storing of Build Job results (compiled c++ object files) for possible usage within a subsequent build.
This can avoid repeating the work, and hence a significant performance benefit.
The check within the Cache is a Cache Lookup and a positive result is a Cache Hit, and conversely a negative result is termed a Cache Miss.
Terms not specific to the Turbo Build Accelerator.¶
Mostly these are Microsoft terms :
Microsoft Visual Studio IDE¶
The Integrated Design Environment (IDE) is an application to view, edit, organise and build source code files.
Builds launched from this application will use the MSBuild tool.
Microsoft Visual Studio MSBuild msbuild.exe¶
The Microsoft MSBuild tool is responsible for interpreting a Visual Studio Solution and/or Project and launching the necessary build steps.
Of primary interest are the c++ compilation steps. msbuild.exe will launch the Microsoft compiler cl.exe, or if configured to build with Turbo, it will launch the bin\turbo-cl.exe Hook process.
This tool can be used from the Visual Studio IDE or from a Microsoft Command Prompt for headless builds.
Microsoft Visual Studio Extension (VSIX)¶
The Visual Studio application can have its functionality extended by being able to install Extensions.
These Extensions are typically non-Microsoft in origin.
An Extension installer has a .vsix file name.