On Thu, Nov 13, 2008 at 02:05:20PM -0700, Roger Pack <[EMAIL PROTECTED]> wrote:
> 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?
Hrmm.. it is defaulted to some hopefully sane value - if you specify it,
that's w
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
What seems to happen is that when I'm within the 'main' ruby dll
sockets work like a champ, then when control transfers to the libev
side for some reason all socket functions don't work. You can't even
bind to a fresh socket there or anything.
My latest guess is that there is some inconsistency w
On Mon, Nov 10, 2008 at 10:35:08PM -0700, Roger Pack <[EMAIL PROTECTED]> wrote:
> This overcomes compile errors similar to:
You forgot to atcually mention the error messages in your mail (you only
included a harmless warning message).
Which errors do you actually get?
--
The cho
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:
