RE: Re: Recursive externals problem

Yes, I should have explained our svn directory structure first...

Following is the layout of our project directory:
projectA\
  |-bin\
  |-lib\
  |-include\
  |-src\
  |-depend\
So externals will put all depending projects in the "depend" folder, after we do a development build, the outputs will be put into the "bin", "lib" and "include" folders, then these outputs will be committed to the svn, so other projects which depend on this project can reuse the development build outputs, thus no need to build the depending projects again. This is to save build time during development.

Back to the projectA, projectB, projectC and projectD example. In this case when we try to build projectD, the only project involves in the build is the projectD itself, as projectA, projectB and projectC already have their build outputs ready when they are checkout from svn, projectD will reuse those build outputs during it's build.

This is my way of managing development build, may not be the best way of course. Anyone who like the discuss on the "managing development build" related issues are welcome also.

We have different strategy on the build server/production build, but those are no longer related to this "recursive externals" problem I raised.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=982647

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-11 20:38:04 CET