Al Hoang

Just wanted to let folks know that I’ve finally figured out how to get the build system in place for ruby-opengl to:

• Gemify itself
• Build native extensions during Gem installation using mkrf

Which means (I hope) that there should be an easier way to get OpenGL working with Ruby. Currently it should support installing in Linux and OS X. Installation should be as difficult as:

gem install -y ruby-opengl

Deinstallation should be similar.

For win32 users, I’d suggest using the old bindings provided with the all-in-one installer although I’d like to get a gem built for win32 so hopefully it can get included in the all-in-one installer.

References

• rb-opengl in Darwin.. err MacPorts
• An older way to get OpenGL in Ruby on OS X working

If you’re seeing tons of those messages like I’ve been and wondering what in the world that is all about. After Googling around I finally found a definitive answer on Jason Young’s Blog what it was all about.

What is it

Since rubygems 0.9.0 the command require_gem has been deprecated in favor of just plain gem. Part of the reasoning for it going the way of the dodo is tied to some
problems with autorequire. I don’t know any of the deep voodoo that powers rubygems but uh.. okay.. sure.

How to fix it

If you’re still getting these warnings you’re recommended to try re-installing all gems you might have installed if you have a 0.9.0 or lower installation. Happy Ruby Hacking.

References

• My those deprecation warnings are annoying
• Gem deprecation redux
• Autorequire is gone
• Rubygems mailing list post on autorequire issues