[Top][All Lists]

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

Re: Sharing a repository directory amongst multiple projects?

From: Todd Denniston
Subject: Re: Sharing a repository directory amongst multiple projects?
Date: Thu, 17 Apr 2008 17:18:32 -0400
User-agent: Thunderbird (X11/20080213)

Kevmeister wrote, On 04/16/2008 06:12 PM:
Hi. We are developing on Windows. Many of our projects rely on third-party
libraries which have their own sets of header files and which undergo their
own revisions over time. So, for our example, V1.5 of "OurProject" might be
using V1.2 of "Third-Party-Comms-Library". So clearly any particular version
of our code is matched to a particular version of the Comms Library.

The goal we are trying to reach is that when we check-out a particular
version of our project, we get all the necessary files required to build it,
which includes the correct version of the third-party library headers (and
would also include the correct version of the library files themselves).

Is there any way of adding some kind of "link" in CVS that appears as a
plain directory on check-out but whose job is to retrieve content from a
particular version (or latest version) of another directory in repository?
Our current approach is to simply copy the required files (headers, lib
files) so they exist in two places in the repository.

For example:

    /third-party-library-name   ---> contains files from
"/third-party-library/include", Version 1.0

I have looked at "modules" (aliases etc) but that didn't seem to be what I
needed. Any other suggestions are greatly appreciated.


The usual way to handle these kind of things is to use your build tool (make in Unix, Ant with java, or a script the user knows they need to run) to either create the "soft link" or copy the appropriate version of the third party lib into the environment from a common location. by using this method, which version of the third party lib becomes versioned along with the rest of your code.

the above assumes that the third party lib is binary.

if it is source code then you could have the same build tool do the appropriate command to check out the correct version.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

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