From: Danny van Bruggen <danny@...>
Date: 2002-01-12T07:58:46+09:00
Subject: Re: Fixing RUDL C extension and Ruby for Visual C

> > win32\makefile looks like this (rubyw_install_name was added
> > manually)

> It's not needed (OK to be), append this line at last instead.

> $(PROGRAM): $(WPROGRAM)

> # Well, it's not been included yet?

Hmm, how do you mean? I haven't tried it, if it works, it really should be
in win32/readme, since that says "And add ((|RUBYW_INSTALL_NAME|)) to
change the name of the executable without console window if also you
want."

> > > > - 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"
> > > (snip)
> > > > -e:1: parse error
> > > > File::install(ARGV[0] ARGV[1] 0555 true)
> > > >                                   ^
> > > > Where did the comma's go? They are there in the makefile...
> > >
> > > What shell do you use?
> >
> > Win98's command.com.
>
> Sorry, no idea about the curious behavior.  I've never built
> mswin32 version with Win98's command.com, but only on cygwin.

I fixed it with the same quoting trick. I changed single quotes around the
commandline options to double quotes. Like this:

---
$(archdir)$(target_prefix)/$(DLLIB): $(DLLIB)
        @$(RUBY) -r ftools -e
"File::makedirs(*ARGV)" $(rubylibdir) $(archdir)$(
target_prefix)
        @$(RUBY) -r ftools -e "File::install(ARGV[0], ARGV[1], 0555,
true)" $(DL
LIB) $(archdir)$(target_prefix)/$(DLLIB)
---
... and more. Now it doesn't remove the interpunction anymore.

Does it matter for other platforms if the quotes are double, not single?

Danny