> I don't do builds where the source-tree and build-tree are different,
> but I'm fairly confident that if I *was* to do this, the build-tree
> would lack the non-SWIG-generated Python modules (the 'svn' stuff, not
> the 'libsvn' stuff).
I built JavaHL with different build and source trees, and it worked
beautifully. I haven't tried it with SWIG yet.
> Also, the SWIG-generated Python modules need to be built into into a
> 'libsvn' subdirectory (preferably a sibling of the 'svn' subdirectory)
> so that they can be referenced as the 'libsvn' module.
Ok, looks doable.
> I think once those two things are solved, a test framework could add
> the common parent directory of the build-tree 'svn' and 'libsvn'
> directories to sys.path (at the head of the list, of course, to
> override any installed bindings), and then could import those modules
> and test exactly as you would if 'svn' and 'libsvn' were installed.
Beautiful. That's exactly what Perl does (they create a 'blib'
directory and install everything there to start, then copy everything
out to the main install directory)
> Oh! And also, ideally, build-tree C-based modules would link against
> build-tree Subversion libraries (not the installed ones).
That's doable. Would we need to relink everything to do the main
installation? If we did have to relink everything, would that be a
problem?
> Hello? David? Are you still around? Have you run for the hills yet?
> :-)
I'm still on board :)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 2 22:55:13 2004