On Wed, Nov 19, 2008 at 3:13 PM, Dominic Sisneros <[EMAIL PROTECTED]> wrote: > The link was to show that they suggest putting the dll files under > c:/ruby/lib/ruby/1.8/i386-mswin32 if compiled with mswin32 and under > c:/ruby/lib/ruby/1.8/i386-mingw if compiled with mingw, msys chain. That > way, you could use the same pure ruby libraries if you rename ruby mingw > version of executables to rubym and irbm and have the specific i386-mingw > directory added to the PATH for mingw extensions. >
That's the way extension installation and site_ruby used to work (this was pre-rubygems world). Under that scenario, when you installed a newer version of a extension it override the previous one, simple as that. With gems, things can co-exist and thus, landing in a shared directory (btw, which already exist) will not be an option with gems that can depend on the same dll name but different versions. Right now you have i386-msvcrt that indicates the dependency on MSVCRT.dll, for both MinGW and VC6. -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams _______________________________________________ Rubygems-developers mailing list Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
