On Friday 23 December 2005 01:12, gogins@pipeline.com wrote:

> I see no such discussion in the liblo-devel list (the only liblo list that
> I could find).
> 
> With MinGW and MSYS on XP Home Edition, I can compile liblo OK, but the OSC
> opcode won't link properly in SConstruct. Complains about missing symbols
> (see below).
> 
> But these symbols are (mostly) in the libws2_32.a library, which is in the
> link line.

The problem seems to be that the symbols in libws2_32.a have __stdcall
linkage (and names with a suffix like @16 etc.) while liblo for some
reason expects __cdecl. Is it possible that instead of #including the
correct header file, liblo declares the functions explicitly, forgetting
to add __stdcall ?


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net