[Win32utils-devel] installing event.so

win32utils-devel at rubyforge.org win32utils-devel at rubyforge.org
Thu Mar 11 08:43:16 EST 2004

win32utils-devel at rubyforge.org wrote:
> Great ! Thanks ...
> Two questions:
> 1. Are there any (more) dependencies between the different win32utils
> modules?
> For example:
>      C:\win32utils\win32-mutex\test>ruby test.rb
>      c:/ruby/lib/ruby/site_ruby/1.8/i386-msvcrt/win32/mutex.so: No such
> file to load -- win32/ipc.so (LoadError)
>         from test.rb:7
> If there are, can we document them somewhere?

You can blame Park for this ;).  Yes, it will be documented.  I hadn't
gotten around to it yet because we haven't "officially" released
win32-ipc.  Sorry for the confusion.

> 2. There seems to be a proliferation of win32 directories in the c:\ruby
> directory tree.
>     C:\ruby>dir /b win32 /s
>         C:\ruby\lib\ruby\1.8\win32
>         C:\ruby\lib\ruby\1.8\i386-mswin32\win32
>         C:\ruby\lib\ruby\site_ruby\1.8\win32
>         C:\ruby\lib\ruby\site_ruby\1.8\i386-msvcrt\win32
>         C:\ruby\lib\ruby\site_ruby\1.8\win32\win32
>    If we are putting all our win32utils modules in one dir can we name
> it as "win32utils" instead of  just "win32"?
>    This may be a question for wider audience (ruby-talk)?

They should all be under site ruby.  I think the last one,
C:\ruby\lib\ruby\site_ruby\1.8\win32\win32, was caused by a quirk in the
way mkmf and win32-eventlog install things.  I *think* I fixed it.  My
guess is that you have mc.rb under that directory.

As for the others, I believe part of the reason is the way mkmf works
with regards to .so files versus pure Ruby files. Also, you may have
done "make install" instead of "make site-install" (?).

Generally speaking I've noticed that mkmf needs work. ;)


More information about the win32utils-devel mailing list