On 8/20/06, David Glasser <glasser@mit.edu> wrote:
> On 8/20/06, glasser@tigris.org <glasser@tigris.org> wrote:
> > New Revision: 21134
>
> > Log:
> > * INSTALL
> > Various changes because we're shipping deps separately.
>
> I'd appreciate eyes on this change, as I'm not a build system expert.
>
> Specifically, in the section about building from a checkout:
>
> > @@ -461,8 +482,8 @@
> > the ./configure script. This enables debugging symbols in your
> > binaries (among other things) and most Subversion developers use it.)
> >
> > - Unlike the pre-packaged tarball (which includes apr, apr-util,
> > - and neon subdirectories), ./configure will fail if it cannot
> > + Unless you've gone out of your way to unpack a Subversion dependency
> > + package onto your checkout, ./configure will fail if it cannot
> > find apr, apr-util, and neon libraries already installed on your
> > system.
>
> I'm not sure if this is true or not: is the reason that ./configure
> doesn't work without deps installed in a checkout merely because the
> deps aren't there, or because there's special code in the release
> tarballs to look for them? The above change was assuming the former.
I'm not sure what you're asking... Configure works just the same in a
release tarball as it does in a regular svn checkout. One thing to
point out is that neon is optional though, not finding it won't make
anything fail, we just won't build ra_dav.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 21 05:53:34 2006