[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:externals and shared projects

From: Oliver Frick <gutenabend99_at_yahoo.de>
Date: 2006-08-30 19:18:23 CEST

Hello Sander,
we had a similar problem in our workgroup and have found
the following solution to be useful:

Our repository is subdivided into basic directories:
/apps, /lib, /projects (and others)

Every application subdirectory contains only it's own resources
(source code etc), but no libraries, not even externals-refs to them.
For every application we create a second subdirectory (currently
located in /projects) that pulls together the application's stuff and
additional resources. Everything is linked via externals properties
here. The externals properties assemble a compilable application
by placing all resources in a directory structure that mirrors our
repository top-level, i.e.

/myAppProject/apps/myApp (here without the trunk/branches etc)
/myAppProject/lib/libB ... etc.

The make files of the application (or a VisualStudio project etc.)
can then be configured to look for the additional stuff
in the respective directories relative to the checked-out app-dir
(e.g. "../../lib/libA").
It works even better for us, since we use our applications in
different configurations. Some applications are not only used standalone
but sometimes as part of a larger project consisting of multiple
apps, so the libraries - which are used in many of our applications -
would have to be checked out and compiled multiple times. With
the method above they are only checked out and compiled once for
all applications in the project.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 30 19:35:03 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.