From: Danny van Bruggen <danny@...>
Date: 2002-01-10T21:03:06+09:00
Subject: Fixing RUDL C extension and Ruby for Visual C

Hello all,

A few days ago I've tried to get my extension library to work with Visual
C (on win98). Here are a few things that went wrong:

About compiling Ruby with Visual C:

- It would have been nice to mention that the Ruby source shouldn't be
unpacked in a directory with spaces -before- the installation instructions
:)

- After editing the makefile to build "rubyw" (no console Ruby
executable), nmake still didn't build rubyw.exe. I had to do an additional
"nmake rubyw" for that, and the resulting exe doesn't work so well. (See
binary on my site)

Compiling my extension with Visual C:

- When I try
ruby extconf.rb --with-whatever=somethingelse
the equal sign will be removed by the shell(?) and you end up with
"--with-whatever" set to true instead of "somethingelse". This can be
fixed a bit by quoting:
ruby extconf.rb "--with-whatever=somethingelse"

- When I do "nmake install" to install my extension, I get the following:
>nmake install

Microsoft (R) Program Maintenance Utility
Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.

-e:1: parse error
File::install(ARGV[0] ARGV[1] 0555 true)
                          ^
-e:1: parse error
File::install(ARGV[0] ARGV[1] 0555 true)
                                  ^
Where did the comma's go? They are there in the makefile...

... the results can be found on http://rudl.froukepc.dhs.org/ including
the VC Ruby 1.6.6 build and a log of what I did to compile everything.

Danny