Hi,

At Wed, 19 Jul 2006 14:49:28 +0900,
Charlie Savage wrote in [ruby-core:08267]:
> When I build an extension with VC++ 2005, the extension links against
> msvcr80.dll (never had compile/link issues with the Ruby headers and
> libraries).  Which means that two CRTs are now in play, msvcrt.dll and
> msvcr80.dll (which is also dependent on msvcrt.dll).  At this point you
> have to be careful about passing CRT resources between the two CRTs or
> else you'll crash the program.

And you have to count external DLLs - Iconv, SSLeay, PDcurses,
etc.

> And I'd guess this is where my experience is different - for the
> extensions I've built the communication between the extension and Ruby
> has been done only via the Ruby C API.  There haven't been any examples,
> like you mention above, where Ruby and the extension communicated via a
> CRT function such as get_errno and set_errno.

Can you let other products use Ruby API?

The possible (and perhaps the only) way would be compiling all
sources by yourself.

-- 
Nobu Nakada