David James <staple@gmail.com> writes:
> > > I think the only caveat is that you might have to install it first
> > > before running tests. There might be some creative ways around that,
> > > but libtool is going to make it more difficult than it has to be.
> > That's the caveat that keep me down. We need to be able to do
> > in-place (that is, in-build-dir) testing before folks install.
> I agree. I'd be willing to work on this issue. What issues need to be
> worked out before I begin?
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).
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.
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.
Oh! And also, ideally, build-tree C-based modules would link against
build-tree Subversion libraries (not the installed ones).
Hello? David? Are you still around? Have you run for the hills yet?
:-)
---------------------------------------------------------------------
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:43:51 2004