Re: [RubyInstaller] DevKit for ruby 1.9.3 with g++ 4.7? (C++11 feature needed)

[Luis Lavena]

Hello,

On Thu, May 2, 2013 at 5:56 AM, Pierre Yves LE BORGNE <pierre-yve...@codecasesoftware.com> wrote:

Hi,
I read a bit of this thread ( https://groups.google.com/forum/?fromgroups=#!searchin/rubyinstaller/4.7/rubyinstaller/nWadNZEBR9k/O7WRdhkt5cEJ ) but didn't understand everything of it :p .

What I'd like to do is having a DevKit for compiling ruby C++11 extensions, for ruby 1.9.3. The problem is that the DevKit I got has a g++ 4.5, and my C++ code uses template aliases which are implemented only since g++ 4.7.

Is there a DevKit for ruby 1.9.3, with a GCC 4.7 (or newer) ?

There is no official release. The official ones at our website are with GCC 4.5.2, and that will be always (during the lifetime of Ruby 1.9.3)

That is simply because introducing that massive change between patchlevels will bring more confusion and I learnt that *people do not read instructions, ever*

Ruby 1.9.3 does compiles with GCC 4.7.x, but is not officially released. The difference is not just version of GCC but capabilities of the different toolchains. mingw (tdm-1 release) is different from mingw-w64 one.

You have two alternatives: build your own version using RubyInstaller repository, or use the automated builds available in RubyInstaller CI:

http://ci.rubyinstaller.org/job/rubyinstaller-1_9_3-x86-package/

The automated builds use GCC 4.7.1 (mingw-w64) and are continously build by newer commits of the branches (in this case, 1.9.3 one)

Please note even this is officially unsupported, if you use it and detect any problem, we will take your feedback to avoid next versions of RubyInstaller and Ruby have those issues.

Let me know if you have further questions.

--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry