Build Gosu Gem?

By jlnr (dev) Date 2012-05-28 12:58

rake windows:gem / rake mac:gem / rake linux:gem, which I usually run from my OS X machine.

But the Windows task needs the "RubyGosu" project built via MSVC, and both .so files need to be copied into lib manually.

The OS X gem uses xcodebuild to precompile the gem. However, the release process has not been updated for Xcode4 yet and the Ruby 1.9 part of it is rather exotic too. If you just want to try new things on OS X, you can simply use rake linux:gem to build the source gem and then install it - which works fine on OS X too.

By RavensKrag Date 2012-05-28 18:23

I'm just trying to get it to work on Linux, as that's my primary platform (I actually don't have access to a OSX machine, that other thread was for someone else on my team). Trying to see if I can't fix that input problem :D

But regardless....

So I run rake linux:gem and get
'rake aborted!
uncaught throw "GOSU_RELEASE_VERSION must be set"

Tasks: TOP => linux:gem => set_version
(See full trace by running task with --trace)'

But env GOSU_RELEASE_VERSION='0.7.44' rake linux:gem gives
'rake aborted!
can't modify frozen String'

The trace is here
https://gist.github.com/2820385

Modified the setting of the GOSU_VERSION variable a bit to create a new string (my current implementation is a bit kludgey) to get around this. I assume you don't have this problem when you build though, so I'm wondering what the difference is.

By jlnr (dev) Date 2012-05-29 02:33

I am using Ruby 1.8 for rake stuff on my system. Also, Rubygems and Rake are both very brittle in my experience. Does that not look like a Rubygems bug right there? :) Does updating Rubygems help? Otherwise I think GOSU_VERSION.dup should do the trick.

By RavensKrag Date 2012-05-29 03:33

It feels like a difference between 1.8 and 1.9 bug, honestly.

#dup is probably a better, cleaner way. I'm currently doing something like GOSU_VERSION = "#{version}".