I'm currently in the process of converting source in SCCS to Perforce (in UNIX) and I was hoping that I could get some thoughts on the following:

# From a common library source tree we compile both single and multi-threaded lib's. We want to maintain separate object files for both the single and multi-threaded compiles (in order to support incremental compiles) but would like to maintain the same source base. Previously using SCCS, we had two separate directories, ~/lib and ~/lib_r and linked the SCCS directory in ~/lib_r to the one in ~/lib.

As far as I can tell, Perforce does not allow multiple client mappings for any given depot file within the same client specification (which makes sense). For example, I can't do the following in a client view: //depot/lib/... //myfiles/lib/... //depot/lib/... //myfiles/lib_r/...

The options that I have thought of is to create a branch but then we would have to integrate at every change. That option isn't too bad since I can do the integrate automatically using triggers. The second option is to use symbolic links to either have a copy of the files within another directory or to rename the files to something else.

Does anybody have an easier solution?

Thanks.

*********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***********************************************************************