We've been able to do something like this using makefiles. There are a common set of files that define the procedures how to do certain tasks(checkout,build,etc) and every module/app has a makefile that is just included into whatever project you are working on.
We have been using this successfully for about a year now with no major complaints. The biggest benefit that for people working on multiple projects, every project is built in the exact same way so there is no learning curve about how to checkout and build a project. We are using our own make program so I'm not sure how this methodology would transfer to other makes.
Tony
------------------------------------------------------
Tony Cleveland
Development Manager - MicroStation Schematics
Bentley Systems, Incorporated
voice: (301)926-0802 fax: (301)926-2313
email: [EMAIL PROTECTED]
------------------------------------------------------
-----Original Message-----
From: Gerhard Sittig [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 07, 2000 2:33 PM
To: [EMAIL PROTECTED]
Subject: Re: including and linking from multiple CVS projects, part 2
f'up-ing to myself ...
On Thu, Sep 07, 2000 at 20:29 +0200, Gerhard Sittig wrote:
>
> [ ... ] It turns out you need a Makefile in every module's root
> describing how to generate the module's target libraries [ ... ]
Just while I see the subject line again: Header files seem to be
the module's target just as well as the lib is. So they should
be "built and exported" just like the libs are. Get this into
consideration and I guess you're done.
virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76
Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED]
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
