Installing and Building Your SourcePro® C++ Products : Chapter 2 Quick Start : Results of Running a Buildspec
Results of Running a Buildspec
Running a buildspec produces a set of build artifacts. These include a directory structure and a build report, as described below.
Directory Structure
The directory structure produced by the execution of a buildspec is not always the same. The structure depends on the components that were built and the build configuration.
The figure below shows the directory structure resulting from a build of the Essential Tools Module and Threads Module trace package in the 12s build configuration.
Directory Naming
The name given to the configuration directories, 12s in this example, depends on the build tag naming convention you choose. These examples use the SPM naming convention, 12s.
With the RCB naming convention, these names would be ms; with Verbose RCB, _NativeStdLib_Win32ThrLib_Static_Release. (“Build Tags” explains naming convention options.)
Directory Structure Variations
The buildspace directory structure can vary in the following ways:
• The examples directory exists only if you are building examples.
• The contents of the 3rdparty directory depends on the modules you have installed. For example, installing the Internationalization Module creates a 3rdparty directory that contains third-party components such as ICU library files.
In addition, an export buildspace directory structure can vary in the following ways:
• The docs directory does not exist for an export buildspace.
• The 3rdparty directory also does not exist because an exported build references the directory in the original install location.
• The source directory of an export buildspace contains the configuration directories where products are built, but does not contain source files unless the copy source and headers option was selected.
• The records directory of an exported buildspace does not contain the libraries subdirectory.
Chapter 4 explains how to work with buildspaces.
Build Report
Detailed build information is available at:
 
buildspace\records\results\buildtag\index.html
You can access this file by one of two ways:
• Go to the directory where index.html is located and open the file.
• Click the Browse Output button at the bottom of the build manager screen and then click the build you want to view. This is available only in the GUI.
This is the best starting point for information useful in debugging and building your applications. At the top of this file is a build summary table. Click a link in the Name column to display a list of the libraries built for that particular module or package, and then click a library name to view the log file for the library build. Examining the build report allows you to view the actual command line invocations used in the build.