I believe on windows it reports error selectable when there's an error
with the socket. I think LIBEV probably just translates it as
readable or something :)
-=R
___
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/cgi-bin/mailman/listi
On Wed, Nov 19, 2008 at 5:53 PM, Jim Lloyd <[EMAIL PROTECTED]> wrote:
> Roger, thanks for the reply.
>
> Forgive me if I am being dense, but the links I see at the bottom don't lead
> me to any unit tests.
>
> As for sample programs, I see some references to programs that use libev,
> and I expect
There's a link at the bottom of
http://software.schmorp.de/pkg/libev.html
___
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
Thanks for doing that.
I would also note that [after switching the link order to be -lws2_32
-lmsvcrt-ruby-190 [i.e. making ws2_32 come first] the bindings for rev
and mingw work splendidly with the latest version of ruby {1.9}].
Increasing FD_SETSIZE past the [msvcrt6] limit of 512 also seemed to
Appears that for windows [at least currently] you don't need to
specify EV_SELECT_IS_WINSOCKET 1 since it's auto-set is that right?
For my instance I discovered that attempting to do:
#include
#include
#include "ev.c"
/* now do some ruby stuff that uses libev */
caused conflict as some #def
ere is some inconsistency with linking to
-lws2_32 within two separate .so files and expecting sockets to work
within both. Tough to tell though.
Oh well...cruddy wiindows :)
-=R
On Wed, Nov 12, 2008 at 2:40 AM, Roger Pack <[EMAIL PROTECTED]> wrote:
> Note that for some reason, adding
I wonder if it would be possible to add IOCP (to emulate event driven
architectures) to libev.
http://code.google.com/p/spserver/ might have a working libevent with
this style architecture..
http://www.eggheadcafe.com/software/aspnet/32292639/integrate-windows-io-com.aspx
seems to explain how.
Two
As a note [in case there are followers], appears that for
configure.make
to work in a mingw environment,
ev_win32.c and event.h
both need (for some reason)
#include
#include
at the top [for the timezone/timeval structs].
This overcomes compile errors similar to:
In file included from event.c:
trying to compile rev [based on libev] for mingw in windows, I sent it
fd "3" [an accepting socket]
and got
Assertion failed: ("libev only supports socket fds in this
configuration ", ioctlsocket (anfd->handle, FIONREAD, &arg) == 0),
file ../libev/ev.c, line 729
where apparently anfd->handle was
