[Rubyinstaller-devel] Non-working gems (like id3lib-ruby)
luislavena at gmail.com
Tue Dec 2 20:22:03 EST 2008
On Tue, Dec 2, 2008 at 5:16 AM, Charles Roper
<reachme at charlesroper.co.uk> wrote:
> Hi Folks,
> I've been trying out the MinGW version of Ruby and have come across a few
> gems that don't install. Most of these, I think, are already known about
> (like hpricot), but some others perhaps aren't. Is it worth me posting those
> that I have tried to install but had problems with, or is it not worth it?
Well, collecting a list of these gems will be helpful, maybe a
blacklist of gems and the contact information of the developer for us
to poke them? ;-)
> Should I instead contact the author of the gems directly?
Yes, indeed, and point them to integrate rake-compiler, which soon
will get the rubyforge project approved ;-)
> The latest non-working gem I have found is id3lib-ruby.
> This requires the id3lib C++ library. The author provides a precompiled
> version for Windows, and for Linux/OS X you have to install it using
> aptitude (or whatever).
> In the light of Luis's rake-compiler, what would be the best way of
> improving the installation of this gem?
If the project is in github, fork the project, integrate the
enhacements using rake-compiler and send a pull request to the
if they are using subversion, try to generate some patches.
Either the new RubyInstaller and the cross compiler have stdc++, so
build c++ extensions will be easy.
> Another gem that breaks under MinGW is proj4rb:
I have no knowledge of those, but let's add those to a black list in the wiki?
Thank you Charles for your time on this!
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.
More information about the Rubyinstaller-devel