Hi folks.
I've added a page to Ruby garden documenting how I built Ruby 1.8.2
(stable snapshot) for Windows:
http://www.rubygarden.org/ruby?HowToBuildOnWindows
I had considerable assistance in this process from the folks in #RPA
-- thank you. I'd be interested in suggestions for improving either
the instructions or the process.
Regards,
Matt
Wow, Matt, nicely documented!
On Fri, 29 Oct 2004 07:01:14 +0900, Matt Mower <matt.mower@gmail.com> wrote:
Hi folks.
I've added a page to Ruby garden documenting how I built Ruby 1.8.2
(stable snapshot) for Windows:
this is getting to be a ****ing joke.
i'm sick of people moaning about the
solutions that may provide problems
for accessibility restricted people
cus until we get complaints frankly
i don't think we should waste our
time. will someone PLEASE FIX THE
FREAKING WIKI IMPLEMENTATIONS???
Alex
On Fri, Oct 29, 2004 at 07:01:14AM +0900, Matt Mower wrote:
Matt Mower ha scritto:
Hi folks.
I've added a page to Ruby garden documenting how I built Ruby 1.8.2
(stable snapshot) for Windows:http://www.rubygarden.org/ruby?HowToBuildOnWindows
I had considerable assistance in this process from the folks in #RPA
-- thank you. I'd be interested in suggestions for improving either
the instructions or the process.
very nice. You could have asked for the main page of rubygarden, maybe 
Anyway, something that could be added is: wat extension libraries got compiled?
how to allow the compilation of elements of the standard lib such as zlib/curses/openssl? Wich packages am I supposed to get ?
Hi,
Matt Mower wrote:
I've added a page to Ruby garden documenting how I built Ruby 1.8.2
(stable snapshot) for Windows:http://www.rubygarden.org/ruby?HowToBuildOnWindows
I had considerable assistance in this process from the folks in #RPA
-- thank you. I'd be interested in suggestions for improving either
the instructions or the process.
Nice work.
What exactly is the benefit of linking the modules statically? Why would you want do do that (as it's apparently not the standard setting)?
Happy rubying (and building)
Stephan
Anyway, something that could be added is: wat extension libraries got
compiled?
how to allow the compilation of elements of the standard lib such as
zlib/curses/openssl? Wich packages am I supposed to get ?
This is an interesting question. My understanding from editing
ext/Setup and the build results is that zlib, curses & openssl
*should* be in there... however:
Matt@KISMET ~
$ irb
irb(main):001:0> require 'zlib'
require 'zlib'
LoadError: No such file to load -- zlib
from (irb):1:in `require'
from (irb):1
irb(main):002:0>
So something isn't quite right. Given my lack of experience with
Ruby, and the minimal-learning approach I took to building it, this is
perhaps not an unexpected result.
On the other hand I do want to get this to work properly so I will
endeavour to work out what's wrong and fix it.
Regards,
Matt
On Fri, 29 Oct 2004 17:43:58 +0900, gabriele renzi <rff_rff@remove-yahoo.it> wrote:
I'm not sure what you mean. Can you please explain?
Regards,
Matt
On Sun, 31 Oct 2004 20:23:54 +0900, Stephan Kämper <stephan.kaemper@schleswig-holstein.de> wrote:
> I've added a page to Ruby garden documenting how I built Ruby 1.8.2
> (stable snapshot) for Windows:
>
> http://www.rubygarden.org/ruby?HowToBuildOnWindows
>
> I had considerable assistance in this process from the folks in #RPA
> -- thank you. I'd be interested in suggestions for improving either
> the instructions or the process.Nice work.
What exactly is the benefit of linking the modules statically? Why
would you want do do that (as it's apparently not the standard setting)?
Hello Matt,
You should get libz (or so) and openssl library... This link
~ http://sourceforge.net/project/showfiles.php?group_id=7382
might help, but I remember having to build openssl with quite a few
compile-foo tricks.
best regards,
kaspar
hand manufactured code - www.tua.ch/ruby
Hi,
Matt Mower wrote:
What exactly is the benefit of linking the modules statically? Why
would you want do do that (as it's apparently not the standard setting)?I'm not sure what you mean. Can you please explain?
Sure.
The section "How to compile and install" of the README file in the Ruby distribution states ()lines 67 ff.):
> 4. Remove comment mark(#) before the module names from ext/Setup
> (or add module names if not present), if you want to link modules
> statically.
> Make this directory your current directory and edit ./ext/Setup?.
> If you're in the MinGW shell and you're familiar with it you can
> use vi otherwise just use whatever windows editor you're used to.
> Remove the # from the beginning of each of the modules but leave
> option nodynamic commented out. Save the file & exit the editor.
The combination seems to imply that you suggest to build Ruby with statically linked modules.
I'd just like to know what's the advantage of this (compared to dyn. linking - which is the default setting, since it's commented out in ext/Setup).
Happy rubying
Stephan
At Captcha you wrote:
Kaspar Schiess wrote:
Hello Matt,
You should get libz (or so) and openssl library... This link
~ MinGW packages repository - Browse Files at SourceForge.net
might help, but I remember having to build openssl with quite a few
compile-foo tricks.
You might also want to check out:
<GnuWin - Browse Files at SourceForge.net;
lots and lots and lots of native ports of *nix libs and utils for Windows.
Randy.
Hi Stephan,
On Sun, 31 Oct 2004 21:23:59 +0900, Stephan Kämper <stephan.kaemper@schleswig-holstein.de> wrote:
The section "How to compile and install" of the README file in the Ruby
distribution states ()lines 67 ff.):> 4. Remove comment mark(#) before the module names from ext/Setup
> (or add module names if not present), if you want to link modules
> statically.
Hmm... I can't remember why I did that. Maybe I read (or misread?)
something? Something to come back to I guess.
If you anyone has any feelings either way please make a note in the wiki page.
Thanks for explaining.
Matt