>
> it introduces another problem.
> If App1Project is checkedout it'll create the following directories.
>
> App1Project
> App1Project\App1
> App1Project\Dll1
> App1Project\Dll2
>
I'm no expert (sorry about the & being backwards earlier), so you'll have to explore. There is a flag for "cvs checkout", -d, which allows you to specify the target directory as something different than the default. It may be that if you put a '-d' after each component module defn in "modules", that the App1Project module will then behave the way you want.
>
> It seems strange and potentially dangerous to me to have 2 copies of
> Dll1 source in 2 different locations on a machine.(and also a pain
> for the programmer to set the source files up twice for whatever
> development environment they're using). Does anyone know of a way of
> grouping modules together but ensuring that the sub modules are
> checked out to the same place if they occur in more than one group?
>
> Cheers,
> James D
Regarding this, what you might really want is a step in your App1 build procedure that will perform the cvs commands to get the DLL projects and build the necessary DLLs. Assuming that you are using some sort of make utilities, you would do this with dependencies. In other words,
xyz.dll depends on xyz.obj and is built with a linker
xyz.obj depends on xyz.src and is built with a compiler
xyz.src depends on nothing, and is built with a CVS checkout command and a second make invocation.
Thus, if the DLL is built by the first app, a second app will find it in the same place, and will just skip those steps. This is probably OK if the apps and the DLLs are actually pretty tightly coupled (say if they are all components of a single product). If the DLLs are actually pretty independent of the application, I might consider a separate "DLL installation" step. That way you aren't embedding details of building each DLL inside each application.
Remember, "it all makes sense once you understand it". Have fun.
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.
