Build in a Team Environment

When several developers are working on the same project, they can share files in two ways:

Your team may also be able to use a shared configuration file, if no drive letters or absolute paths are included with file names in the configuration file. All relative paths in a configuration file specify directories relative to the location of the configuration file. To make a configuration file that your team can share, put it at the root of the directory tree for source files and specify relative paths for all source and target files.

If you cannot use only relative file names, your team can start with a shared configuration file. The developers may be able to share the configuration file by using variables for the drive letters and paths.

Sharing Source Files Only
The simpler approach is to share source files only.

Each developer maintains a personal copy of the codestore, and can take advantage of local incremental C++ builds. Your team can share all source files or extract local copies from the central repository. After refreshing the local sources or accessing the shared source files, each developer must incrementally build in order to incorporate changes made to all sources.

Sharing Sources and the Codestore
If your team runs centralized builds, you can share the codestore and targets, as well as the source files. In this approach, each developer takes a copy of the codestore and sources that may be changed locally. For example, if the centralized build occurs overnight, each developer can update the local cache in the morning. You can make local builds during the day, and check the updated sources back into the central repository at the end of the day for the next overnight build.

For this approach to work, your team must use a common configuration file. You must also build to keep the codestore up to date with new paths and timestamps for the source and target files. These synchronizing builds should be relatively quick.

An advantage of sharing the codestore is that the amount of work to be done by local incremental builds is relatively small, because each developer must incorporate the changes made by only one person to the sources each day. If your team does not share the codestore, each developer must incorporate the changes to all sources into the local codestore. On the other hand, the approach of sharing source files only is simpler and gives individual developers more freedom to modify the personal copies of the configuration file.

Your team may be able to take advantage of features for file change control that allow the following actions on a central repository of source files:



Projects
Incremental C++ Builds
C Compilation
Configuration Files
Codestore


Change a Build Setup
Add or Change Source Files
Add or Change Targets
Build
Checkout, Checkin, or Extract a Source File


Build Options