Comments on: Progress of One-Click Installer (RubyInstaller)

By: Luis

Luis — Wed, 13 Aug 2008 22:44:38 +0000

lastobelus: by building what you mean? create a x64 Ruby or just build the Ruby and the installer in a x64 system?

There are two different aspect for what are you asking:

One is having Ruby built for x64 platform, and the other is make the installer properly behave on a x64 bits installation of Windows.

The first item requires you build the Ruby dependencies (GNU Readline, GDBM, OpenSSL, etc) with a 64bits compiler. Right now the two x64 compilers available are VC2005/2008 in x64 mode and MinGW64 which is not official.

The second one is tightly related to the first one.

In any case, all the x86 applications can be installed inside x64 system under WoW (World of Windows compatibility layer) which enables 32bits applications run inside 64bits OS.

Right now I don’t have a x64 system handy to check it out, so please report all the issues you find to rubyinstaller-devel mailing list here

By: lastobelus

lastobelus — Wed, 13 Aug 2008 22:22:05 +0000

Is there any chance of building the installer on an XP64 system?

By: she

she — Sat, 26 Apr 2008 10:59:32 +0000

Its great to see someone with a lot more knowledge than I have tackle this.

I am using Linux almost exclusively but I do have a windows box, and I must say I am happy with Ruby on windows so far – i write on Linux, and it works on Windows too (sometimes with slight modifications, but thats it)

Thanks for your effort, from my point of view i LOVE these blogs. They contain a lot of info too

(The other blog i like a lot is http://rubyonwindows.blogspot.com/ the snippets are very useful)

By: Luis

Luis — Mon, 07 Apr 2008 15:13:34 +0000

Yes, 1.8.6-p114 sufer from that, that’s why the pre-compiled version I’m offering at http://dump.mmediasys.com/installer3 is form SVN (which this issue is already been fixed).

I suggest you can try rake CHECKOUT=1 to force the use of subversion latest version instead of the packaged source code.

By: sgwong

sgwong — Mon, 07 Apr 2008 06:01:46 +0000

I just noticed that the ruby irb consumed a lot of cpu usage. For other ruby program, this syndrome is not occur. May be it is the problem cause by the Readline library? I thought I had read the same problem before on the forum, but I had forgotten which forum already.

By: Luis

Luis — Thu, 03 Apr 2008 19:05:47 +0000

Great to know it worked for you!

Yeah, some extensions will not compile, basically Zlib, OpenSSL and Readline were the only ones produced right now.

If you want any other of the extensions bundled in ruby code, please feel free to take a look and hack some rake tasks for it, you can see that is not complex at all!

By: sgwong

sgwong — Thu, 03 Apr 2008 10:00:51 +0000

The script works very well. Appreciated for your hard work on it. Although some ruby extension is not able to compile, but it is usable for me now. I had did some benchmark to compare the ruby MinGW with the ruby VC6 and the MinGW gain 10% speed increment. It is a really good news for me.
I had compiled the ruby-gnome with the new MinGW ruby. It is working well also, I had a working ruby with the ruby-gnome binding. Now, it is the time for me to compile all the gems I want.

By: Dr Nic » Writing C extensions in RubyGems using newgem generators (plus a free TextMate bundle)

Tue, 01 Apr 2008 11:54:28 +0000

[...] tutorial is for *nix, as I’m still investigating win32 extensions, and jruby + .net/ironruby extensions. So when I figure that out – hopefully with the help of other [...]