Closed GoogleCodeExporter closed 9 years ago
The latest platform that we support is libjingle 0.5.1 and swtoolkit 0.9.1.
Could you please follow the instruction in the README file (in the libjingle
download package) and try again?
http://code.google.com/p/swtoolkit/downloads/list
http://code.google.com/p/libjingle/downloads/list
Original comment by jun...@google.com
on 16 Nov 2010 at 3:37
Original comment by jun...@google.com
on 16 Nov 2010 at 3:37
same error with libjingle 0.5.1 download package
Original comment by vitalyster
on 17 Nov 2010 at 10:39
Could you please send me the crash-dump so that I can debug on it. BTW, I have
no problem running call.exe on Win7-64bit using the x86 binary.
Have you run into compilation error with the "socket.h" file? If so, how did
you work around this issue? I think if you linked to a wrong version of the
header file, it may be related with the crash, but still need crash-dump (also
the client log file) to figure it out.
Original comment by jun...@google.com
on 12 Dec 2010 at 6:07
I'm just comment out definitions for EWOULDBLOCK, EINPROGRESS, etc. because it
already defined in windows headers. I will try to find crash dump file.
Original comment by vitalyster
on 13 Dec 2010 at 6:27
I'm not sure if it's a right way of doing the build by just comment out those
macro def's. Please take a look at the following article.
http://msdn.microsoft.com/en-us/library/ms737828(v=VS.85).aspx
Original comment by jun...@google.com
on 13 Dec 2010 at 6:45
And what is the solution? I do have the same problem, and I commented out all
redefines. Why all those redefines happening at first place?
Original comment by lytvyn...@gmail.com
on 28 Dec 2010 at 11:46
I am ok about this.
plz follow this build instruction:
http://blog.foolbear.com/2010/11/libjingle5-for-win.html.
Original comment by greatfoolbear
on 29 Dec 2010 at 2:04
Yes, removing /WX from compiler options helps, call.exe connecting and run
without crashes.
Original comment by vitalyster
on 30 Dec 2010 at 1:09
great!
Original comment by greatfoolbear
on 30 Dec 2010 at 5:07
The build issue on Windows should be fixed in 0.5.2. Please use the new package
and report this thread if you still run into the same issue.
Original comment by jun...@google.com
on 15 Jan 2011 at 6:45
Original issue reported on code.google.com by
vitalyster
on 12 Nov 2010 at 10:50Attachments: