Steven Brown wrote:
>
> It works fine with Cygwin, but AFAIK the event loop would need major
> surgery for 'native' Windows/mingw32 as Windows treats sockets
> differently than files, it'd need to have a way to integrate other
> wait handles into the event loop (so no using select/poll), etc..
>
> I'm planning to switch to glib+glibmm for the mingw32 support, but
> glib/mingw32 is currently affected by at least these two bugs that
> cause problems:
>
> http://bugzilla.gnome.org/show_bug.cgi?id=324234
> http://bugzilla.gnome.org/show_bug.cgi?id=338943
>
> Nothing's ever easy I guess. :)
>
Yeah i was using mingw32/msys but as you said the socket stuff does work
differently. I like to avoid having the extra cygwin layer...
Thanks for the tip with glib. I had allready looked into GLibmm and
their Dispatcher for cross thread callbacks (with a MainLoop in both
threads).
I was looking into sigcx because I don't think its possible with the
glibmm to have parameters for the cross thread signals. (In other words
to evoke a call to a function like void mycallback(int) but not bind it
upon connect on the reveiver side. I want to get the values from thread
A to B in with a callback call.)
Or I just haven't figured it out yet...
But am I right to assume that that's not possible with sigcx either?
Niko
|
