>--[Raphael Manfredi]--<[EMAIL PROTECTED]>
> One thing you did mention in our e-mail exchange was that the plain
> standard mingw packages were not enough and that one would need
> a special set of mingw libraries that you provide. Why is that?
Two reasons. First: libxml and gtk/glib >= 2.0 use pkg-config to detect
libraries. Though you can convince pkg-config by hand to find the cross-.pc
files, I modified it to detect cross-compilation and do the right thing.
Those changes will be merged upstream (though possibly in a different
manner) in the next version.
The second: on Windows, library function names are (Pascal-) mangled, that
is, something like @4 is added to the actual (assembler) function name. This
makes detection hard: there won't be a _select symbol in ws2_32, but
_select@<something>, so the detection will fail. My solution to the problem
was modifying dlltool to add the @-less symbol as well to the resulting dll
wrapper (if the --kill-at option is specified and there actually _is_ an @).
Then the generated ws2_32.a will contain _select as well as
_select@<something>, and the detection will just work. If you google around
for function names in Winsocks appended with that mangling you'll find
several people having this problem. Though I reportet it in the Debian as
well as the MingW bug tracking system, I've not yet seen any reply.
--
100 DM = 51 � 13 �.
100 � = 195 DM 58 pf.
mailto:[EMAIL PROTECTED]
http://www.ruediger-kuhlmann.de/
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
Gtk-gnutella-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
