On Sat, Sep 5, 2009 at 3:42 PM, Robert Dailey<rcdailey_at_gmail.com> wrote:
[snip]
>
> 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.
Sure, no problem. This is very likely why it is not supported much in
the first place. As far as I recall, you're the first person to
actually want a totally static build (ie, statically linking apr as
well) on Windows. Subversion used to only supply static libraries
(although it still dynamically linked to apr as it does now) and it
seemed like everyone hated it. There was much rejoicing when the
dynamic libraries were added.
DJ
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2391374
Received on 2009-09-05 23:52:13 CEST