Re: extconf.rb spitting out SH Makefile on windows?
- From: Luis Lavena <luislavena@xxxxxxxxx>
- Date: Mon, 14 Mar 2011 11:38:30 -0700 (PDT)
On Mar 14, 3:17 pm, Mr Eiland <mreiland1...@xxxxxxxxx> wrote:
I ended up moving everything to the mingw toolchain, but I don't
understand why you're saying it's impossible to use Visual Studio.
I'm saying that using Ruby build with MinGW is not possible to compile
extensions with Visual Studio.
At the end of the day the windows loader is the one doing the work, not
the Ruby runtime. Unless you're telling me the dll being spit out by
mingw isn't really a DLL? I would need a more in depth explanation
before I would buy that Windows can load the appropriate DLL created by
mingw, but not the equivalent DLL created by Visual Studio. We're not
talking about compiler specific object files.
Ruby 'mkmf' uses rbconfig, which is generated at compilation time of
Ruby, and is going to use the toolchain defined when Ruby was
compiled.
Beyond altering rbconfig to detect and use Visual Studio, is a matter
of CRT mismatch. This has been discussed in the list and the risk of
memory allocation and free of it due Ruby's GC design can generate
segfaults.
And if you need better answers, you can google for them, described the
problem above the big one, but there are others associated with
compilation flags.
--
Luis Lavena
.
- References:
- extconf.rb spitting out SH Makefile on windows?
- From: Mr Eiland
- Re: extconf.rb spitting out SH Makefile on windows?
- From: Mr Eiland
- extconf.rb spitting out SH Makefile on windows?
- Prev by Date: Re: extconf.rb spitting out SH Makefile on windows?
- Next by Date: Splitting up and Reassembling A File
- Previous by thread: Re: extconf.rb spitting out SH Makefile on windows?
- Next by thread: Re: extconf.rb spitting out SH Makefile on windows?
- Index(es):
Relevant Pages
|
