On Sun, Feb 6, 2011 at 8:15 AM, Owen Shepherd <[email protected]> wrote:

>
> On 6 Feb 2011, at 07:01, Richard Frith-Macdonald wrote:
>
>
> On 6 Feb 2011, at 07:34, Richard Frith-Macdonald wrote:
>
> Thanks, that builds and installs nicely.
>
> But it seems the linker doesn't find it for some reason.
>
> When building base I'm getting 'ld.exe cannot find -licui18n' even though I
> can see that libicui18n.dll has been installed in /mingw/lib :-(
>
>
> Hmm ... my mistake ... libicui18n.dll is of course in /mingw/bin, not
> /mingw/lib ... and the link command is telling the linker to look in
> /mingw/lib, so of course it's not finding it.
> Now I guess I need to figure out why we don't have -L/mingw/bin in the
> command.  Possibly a problem with configure.ac in base?
>
> I'm not really sure what's going on on your machine, it built and links
perfectly on my machine.  I'll try to do a clean install later today to see
if I get similar results.


> Because of the way linking works on Windows, you need to link against a .a
> (.lib for MSVC) file containing import stubs, rather than directly against
> the DLL. The DLL exports symbols with different names from what the compiler
> will expect (Namely, the calling convention mangling is not present in the
> DLL exported symbols)
>

I haven't had this problem, so I'm not sure I can comment.  The one thing I
can say for sure is that the DLLs should be in /mingw/bin or else Windows
won't find them when loading the libraries.  I see a bunch of .a files in
/mingw/lib but there are none for libicu.

Stef
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Reply via email to