Re: Common code base for different projects

[Greg A. Woods]

[ 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,
etc.).

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.

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>