On Wed, Sep 2, 2009 at 4:11 AM, Bolstridge, Andrew <
> From the description, I would think that the apr version you’re using is
> not correct – ie, there is missing code exports.
> See if you can find those exported functions that you are having problems
> linking in the apr sources, or if you’ve built them as dlls, use dependency
> walker to see the exports that the dll is really exposing to you.
> If they are present, then it’s possible you’ve built them as ANSI and
> linking them to an app built as Unicode (or vice versa) and the exports
> aren’t quite matching correctly. The other possibility is that they’re
> imported as declspec(dllimport), but you havn’t built them with
> declspec(dllexport) – ie so they’re exported as standard C functions without
> any MS-specific decoration, but you’re importing them as if they were.
This is very insightful. Thanks, I'll have to check this out. However I must
say, I am just building these libraries with their provided makefiles for
nmake and visual studio. Even if I did manage to find out that one of these
issues was indeed the cause of my linker problems, how would I go about
fixing it? The obvious solution to me seems like to modify the code and/or
build scripts, but I really don't want to have to maintain patches like
Anyway, I'll look into your suggestions and follow up later with results of
my investigation. Thanks again for the great help.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-02 16:39:42 CEST