The Visual Studio Command-line Integration¶
If operating in a non-GUI environment such as an automated build pipeline, then the Visual Studio Extension is not applicable, since the build will be invoked via msbuild.exe.
In this situation you can use the tool turbo-vs-solution-enabler.exe to enable building via TurboDyne for a specified solution. e.g.
The turbo-vs-solution-enabler.exe creates/modifies the Visual Studio Project User (.vcxproj.user) files.
It will also make a small modification to the .vcxproj file to change the Program Database compilation setting from \Zi or \ZI to \Z7. The changes in the .vcxproj will look like :
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
to
<DebugInformationFormat>OldStyle</DebugInformationFormat>
This is necessary to ensure that the debug info is bundled within the compiler-generated object files, to ease the distribution of them throughout the TurboDyne Build Cluster. Additionally, as a side-effect, it ensures that incremental compilation functions correctly.
Use turbo-vs-solution-enabler.exe /help to shows the available options :
c:\Program Files (x86)\TurboDyne\bin>turbo-vs-solution-enabler.exe /h
Version: 2.0.14.0
usage: turbo-vs-solution-enabler OPTIONS
Tool to enable or disable TurboDyne Build for a Visual Studio Solution
/version Print version info
/info Print information
/help Print information
/solution=file Specify the solution file to be processed
/turbo-install-bin-path=path Specify the TurboDyne installation binaries path
/enable-turbo-build Enable TurboDyne Build mode for solution
/disable-turbo-build Disable TurboDyne Build mode for solution
/use-debug-binaries Use Turbo's debug binaries