C++ DLLs built with i586-mingw32msvc and i686-w64-mingw32 are not compatible.

So this changes the build, so that we ship the ports directorys of both
compiler versions.

This fixes https://github.com/larskanis/fxruby/issues/22

The semantics have changed with 54a11707. Only "owned" objects can
be expected to be the same. Borrowed objects can change it's object_id
for each call.

so that all FXTRACE() and FXASSERT() calls are skiped, per default.

This should improve performance.

This fixes https://github.com/larskanis/fxruby/issues/21
It was introduced in commit 347966fc.

This fixes issue https://github.com/larskanis/fxruby/issues/20

it's better to use runOnUiThread in souch a case.

This should ensure, that the event is definitely cleared.

These functions should be thread safe.

Switch off polling-based (addChore) processing of threads

Add event-based interruption of GVL-released functions.

This allows to safely execute GUI code from other threads.

This works for sockets only for now.

This is the only function that is currently required to acquire the GVL.
Other FXRbCall functions could be wrapped equally.

This is just enough for loadPixel/savePixel, but if other methods
release the GVL, potentially all other callback functions could
be called. These are now yet wrapped by gvl-aware wrappers.