Maximizing Your Results with SoftBench
Sharing Projects with a TeamSharing Projects with a Team
SoftBench projects provide the flexibility to have your development environment reflect your team interactions.
Sharing a project description has all the benefits and difficulties associated with sharing any source file. A centralized project description means that everyone is working from the same project files, but there can be collisions when more than one person wants to make changes. You may "break up" your file into several subprojects so that people can work independently and let SoftBench handle the complexities and relationships of the build.
There are several scenarios for partitioning a project:
•One Project, One Author
•One Project, Many Authors
•One Project with Subprojects, Many Authors
One Project, One AuthorWhen your project has only one author, you may want to set up a single project definition.
Alternatively, you can choose to use subprojects to organize your work hierarchically, if that is more convenient. For example, if the subproject is a library, you can modify the build configuration of targets in the parent project to use the library. If you work on both the library and its parent project, using the subproject relationship provides the flexibility to either build the subproject or use it in its current state. If you never want to build the subproject alone, setting up the subproject relationship may not be the best way to structure the project. You can just leave all your targets in one project and use
As your project grows past what one author can accomplish, you face the issues of sharing the work across the team.
The preferred way to work at this level is to designate one person as the owner of the project definition file and have the rest of the team clone
Chapter 1 | 27 |