On Thu, Jan 18, 2007 at 03:27:30PM -0500, John Peacock wrote:
> Byron Brummer wrote:
> >Do all svn developers work like this (nuking their system installs of
> >svn before each build attempt) or is there a saner way in which the
> >build can be isolated to its build directory?
> None of that mumbo jumbo is necessary, as libtool takes care of linking
> to the in-tree libraries during testing and relinking against the
> newly-installed libraries during installation. The sole exception is
> the Perl bindings, which don't use libtool (and I'll be working on that
> soon enough).
There are one or two gotchas, though. For example, if you have an
installed Subversion instance that includes ra_dav, and you then build a
new one without, the new instance will attempt to dlopen the installed
library (because we always try to use the ra_dav library regardless of
whether you built with it).
Debugging can also be a pain if you're dealling with uninstalled shared
libraries, so I tend to build with --disable-shared to make that
easier, rather than fiddle with LD_LIBRARY_PATH etc.
But no, you don't have to blow away your entire installation to develop,
by any means. Those instructions were probably useful when Karl wrote
them five years ago, but they're out of date now -- we should probably
update them (patches welcome!).
Received on Thu Jan 18 21:45:37 2007
- application/pgp-signature attachment: stored