[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: static linking RA libs

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2001-02-16 23:09:43 CET

> Stuff-in-CVS-can-compile is fine. It would be nice to have
> must-link, too. But even with that, we are now requiring the client
> to be linked against DB3. I don't think that's right.

I can see how it's annoying (especially if the build is broken right
now), but I don't see how it's not right, as long as we want ra_local
to exist.

In the long run, as far as the end user is concerned, either
Subversion builds with ra_local functionality or (because they don't
have db3) it doesn't. It doesn't matter whether that's because the
dynamically loaded ra_local module wasn't built and installed or
because the relevant code wasn't compiled and linked in.

> And if I want to spend time on the dynload, then why not? I can set
> my own personal priorities, right? As long as I also meet the
> milestone.

Well, if dynamic loading becomes the only mode of operation for the
client, then it will become harder to debug Subversion. (Even if gdb
actually worked right for shared libraries on all platforms, you
couldn't set breakpoints before the ra module gets loaded, etc.. And
in reality, gdb falls down miserably for shared library debugging on
every platform I've tried it on, for every version of gdb I've tried.)
So we need a way to make static loading work either way.
Received on Sat Oct 21 14:36:22 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.