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

Re: [patch submission] gen-make: Option to statically link APR.

From: Robert Dailey <rcdailey_at_gmail.com>
Date: Sat, 5 Sep 2009 16:42:21 -0500

On Sat, Sep 5, 2009 at 4:35 PM, D.J. Heap <djheap_at_gmail.com> wrote:

> On Sat, Sep 5, 2009 at 12:55 PM, Robert Dailey<rcdailey_at_gmail.com> wrote:
> [snip]
> > I'm re-submitting the patch (attached). It contains fixes to make sure
> the
> > executable projects link to the correct library names. For static builds
> of
> > APR and APR-UTIL, it will find the libraries without the 'lib' prefix
> (e.g.
> > apr-1.lib). And for dynamic builds of APR and APR-UTIL it will look for
> the
> > versions with 'lib' as a prefix (e.g. libapr-1.lib).
> > Let me know if this is an improvement! Keep the code reviews coming!
>
>
> I think this is a little better, but svn.exe still won't link. The
> library directories for libapr*.lib and apr*.lib are different (ie,
> Release vs LibR) and so it can't find apr*.lib when told to statically
> link.
>
> Even when I manually fix those it still won't link because apr is
> pulling in some Windows functions (UuidCreate and TransmitFile) whose
> containing libraries need to now be included in the linker input as
> wel as apr-iconv which is being used by apr-util. All those will need
> to be added to the executable projects' linker inputs and then there
> will probably be more after that. Isn't static linking fun? :)

Yes, I can understand the frustration now. However, this is as far as I can
help. APR's static libraries need to be including these dependencies in its
library, ideally, to avoid any unnecessary complication on SVN's side.
Linking static libraries with other static libraries has proven to have its
own set of problems, but in some circumstances it can save some work. The
patch, as is, just so happens to work well for the libraries themselves. If
the SVN project is still not linking, then it needs to personally include
those dependencies you speak of. How to do this will require a bit more work
on the python scripts, but I don't have the time to try to get SVN building.
My goal was to get the svn libraries compiling against the correct
libraries. Perhaps someone else can pick this up where I left off and get
SVN working?

Sorry to half-ass this, but it's starting to go beyond the problem I
originally wanted to solve.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2391373
Received on 2009-09-05 23:42:37 CEST

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