From: Bob Calco <rcalco@...>
Date: 2001-12-04T03:04:56+09:00
Subject: [ruby-talk:27357] Questions building i586-mswin32 version of Ruby

Hello all:

This weekend I went ahead and built ruby-1.6.5 using the win32 makefiles and
Visual C++ compiler. All works well, except...

* It doesn't automatically make rubyw, I have to do 'nmake rubyw', and move
things over manually. Just wondering if this was intentional, or am I
missing something? I even tried it with 'nmake all', which is apparently the
same as just typing 'nmake'.

* running the ruby-1.6.5/samples/test.rb chokes on line 960 (during 'system'
test), because it can't find "./miniruby ...". First, using cygwin
distribution, there is no miniruby, and it exists in my ./mswin-build
directory. What, if anything, do I need to do to fix this, so the test runs
successfully to completion? Moreover, does it matter? What's the difference
between miniruby and ruby, aside from the fact that miniruby is a lot
bigger?

* The tcltklib from ruby-1.6.5\ext\.. doesn't get made at all (though the
tkutils.so does). So even the simple tk examples that ship with the cygwin
version (pig.rbw) don't work. Comparing it to the cygwin version, it appears
to be the only thing in ruby/lib/ruby/1.6 that isn't made.

* ruby/lib/ruby/site_ruby/1.6 is practically empty -- but that makes sense,
just gotta get the extension I want off the RAA.

* I tried renaming the executables ruby32 and ruby32w, but this forces the
dll to get changed to mswin32-ruby3216, unless I change it. This caused the
win32ole for mswin32 extension module to fail, because it was looking
specifically for mswin32-ruby16.dll. So I went ahead and stuck with the
standard names. I wanted it to be ruby32 because I didn't want it to
conflict with ruby (cygwin) in my PATH, and I could try out the same scripts
using both versions on my system. Any thoughts on other ramifications of
changing the executable names?

I'd also like to understand the licensing a bit better, because I'm
interesting in using Ruby with a commercial application that I'm developing
for my company, perhaps involving some proprietary extensions, or embedded
in it, or both.

I'm also interested in contributing open source extensions to Ruby (I just
applied for a site at sourceforge for wxRuby, which I'm working on, being
something of an admirer of wxPython vis a vis wxWindows).

I want to know what I need to do to keep all these thing separate and
non-conflicting. I'm really hooked on Ruby, and my intentions in using it
with our commercial application are pure. (That is to say: I want BOTH to
make a living AND promote Ruby as the best open-source scripting engine ever
invented.)

Oh, and a quick cygwin question for folks who might know:

I went ahead and downloaded the cygwin environment on my laptop and my
desktop, complete with the dev tools, all the libraries, etc., but on my
laptop, when I try to use VIM, I get the following error:

"The procedure entry point bind_textdomain_codeset could not be located in
the dynamic link library cygint1.dll."

This is not a problem on my desktop, though I don't know why. They are both
very similarly configured, with my desktop having a lot more crap on it than
my desktop (owing to its considerably larger harddrive).

I'm not yet very experienced with this cygwin stuff (I'm still bouncing
around in my head whether it's worth creating a mswin32 version at all, if I
can get good enough at the cygwin stuff, I can do my development in that
where Ruby is concerned, since one of my goals is cross platform behavior,
and I am given to understand that we loose some Ruby functionality with the
mswin32 build. Any advice is welcome.)

I'm also curious to find links to good tutorials on extending Ruby, using
both mswindows and cygwin configurations.

Thanks in advance!

:)

#*******************************************
#* Bob Calco
#* Senior Software Engineer
#* CorTechs, Inc.
#*******************************************
#* rcalco@cortechs.com
#* 703.989.3160 -- cell
#* 703.968.7021 -- office (ext. 120)
#* 703.968.8180 -- fax
#*******************************************