At 3/30/2006 02:39 PM, Garrett Rooney wrote:
>On 3/30/06, Matt England <mengland@mengland.net> wrote:
>
> > I'm looking for perspectives on how to manage the source for these external
> > libraries. I see in the current trunk
> > (<http://svn.collab.net/repos/svn/trunk/>) that there is no 'apr' nor
> > 'neon' directory as documented per
> > <http://subversion.tigris.org/hacking.html#directory-layout>. Are these
> > vendor-external source sets still managed by Subversion? Last time I build
> > svn (from a 1.3.0 tarball) I recall the src tarball including apr and neon
> > software.
>
>We include those in our release tarballs as a courtesy to users,
>they're not stored in our repository, but if the directories are
>present the build system will take advantage of them. In general, I
>don't think most developers actually put apr/apr-util/neon there for
>development purposes, personally I tend to install versions into a
>special --prefix and use that for day to day development.
eg, into /usr/lib & /usr/include or /usr/local/lib &/usr/local/include for
the apr and neon stuff?
>(This is different on windows of course, where you basically have to
>have them as part of your source tree in a location dictated by the
>build system.)
...except for MinGW/MSYS configurations?
Again, if my questions are out of place, please let me know.
-Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 2 06:00:22 2006