[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Common code base for different projects

From: Arcin Bozkurt - Archie
Subject: Re: Common code base for different projects
Date: Wed, 29 Aug 2001 17:33:55 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1

I think the consensus is that I should move those files out to a new module and either manage projects thru the modules file or as mentioned below, or some other way,.

Q) Without loosing the history for those files, how do I move them out of the current module, and create a seperate module for them. Would moving the ,v files in the repository do the job?

Greg A. Woods wrote:
[ On Wednesday, August 29, 2001 at 11:14:00 (-0400), Matt Riechers wrote: ]
Subject: Re: Common code base for different projects

You can put those 'common' files in a seperate module which can be linked in to
the others via the modules file.

Better yet put the common files in a separate module which you
internally manage as a separate product which means separate release
management, etc. Besides the documentation, etc., the primary target
file in this product will be an object library (perhaps in several
forms, just as with system libraries like libc; eg. with profiling
support, with debugging support, as a lint library, as a shared library,

Install the appropriate binary release(s) of your internal library
product on all the appropriate development machines. (use uniquely
named directory names to allow multiple releases to be installed
simultaneously on a given machine)

Then in the build process for each project which shares these common
objects, just link with the appropriate release of your library as you
would with the C library or whatever's germain to your programming
language domain.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]