> > Are you planning to provide (but not officially support) 1.0.0 x86-mingw32 binary (1.9-only or fat?) gems or are you also looking for build patches for this?

> 
> Looking at the stats, a not in-significant number of people install
> the mingw32 binary packages, so it looks like I will upload a binary
> for that.  Before I do that, I'll need someone else to at least run
> the specs against a rake-compiler built mingw32 version, to make sure
> it actually ... works.  That will require someone to fix the
> async-callback stuff in Function.c to work on win32.  (I'm assuming it
> doesn't even compile at all at the moment).

Understood and I think your darwinistic focus is a good choice. If the mingw32 (fat or otherwise) binary is truly valued, patches should eventually flow, right? ;)

I see what you mean re: Function.c.  Doing a "gem install ffi --platform=ruby" using DevKit on 1.9.3dev errors out on 'async_cb_{mutex,cond,call,wait}' and then 'struct gvl_callback'.  I want to look into it.

As your focus appears to be 1.9.2+, are you thinking that future mingw32 binary gems will _not_ be fat?

FWIW, I think as long as FFI can be built/installed on Windows using the DevKit, the fat gem is a nice-to-have if it can't be supported. There's only so much one person has time to do.

Jon
---
http://jonforums.github.com/