Not logged inGosu Forums
Forum back to libgosu.org Help Search Register Login
Up Topic Gosu / Gosu News / Gosu 0.8.4 released
- - By jlnr (dev) Date 2014-09-03 20:42
Today the focus was on all things resolution! I'm not sure what could be more exciting :)

Gosu::available_width & Gosu::available_height can now be used to calculate the available space for a non-fullscreen window. (The return value is only accurate on OS X and Windows for now.)
Gosu::Window::show now respects needsRedraw/needs_redraw? again.
• Fix scaling errors on Retina displays, caused by a regression in Gosu 0.8.3.
Reply
Parent - - By RunnerPack Date 2014-09-18 06:13 Edited 2014-09-18 06:22
I have a problem concerning RubyGems and "platforms".

In the last few versions of Gosu (I think starting with 0.8.0) when I try to "gem update" or "gem install gosu", it says something about the gem not being for my platform, and to use "--platform=i386-mingw32". Since I thought that was the version of Ruby I was using (the output of "ruby -v" even includes the string "i386-mingw32") I started digging around in rubygems to see what was going on, or at least how I could make that the default. I found out that rubygems keeps a list of supported platforms, so I ran "gem env". This produces, among other things, the platforms list: "ruby" and... "x86-mingw32"?!
I'm guessing the problem is that the Gosu gem now targets "i386-mingw32" instead of "x86-mingw32". If this is the case, is there a specific reason for the change? For example, is this the platform returned by the rubygems included with the latest 1.9.x or 2.x RubyInstallers?

I searched the RubyInstaller github for this issue and came up empty. I'm not even sure it's their fault rather than that of the rubygems maintainers themselves. Even if it is, I don't even have the latest build of 1.9.3, let alone 2.x, and I thought that might be my problem, so I want to upgrade before posting an issue.

EDIT: I just updated rubygems, and it still shows the same list of platforms. I'm thinking this is where the problem lies, and I should complain to them about it…
Reply
Parent - - By jlnr (dev) Date 2014-09-18 07:13
Gosu has actually used "i386-mingw32" in past versions: http://rubygems.org/gems/gosu/versions

I don't even remember why I've changed it, I guess it must have stopped working? I also remember vaguely that in some cases, Rubygems would change the string I pass to GemSpec#platform= into another one. (It's probably normalising it.)

If you find out if any platform string is "more right", please let me know :)
Parent - - By RunnerPack Date 2014-09-29 00:09
I think the problem might be the way "gem.bat" (included with the RubyInstaller) calls the gem Ruby script. I just used a mingw bash shell (included as part of the RubyInstaller devkit) to run "gem update" – i.e. I ran the Ruby script directly – and it installed Gosu 0.8.5 without complaint. I then ran "gem list" and it showed both versions of Gosu as being for "x86-mingw32". So, I guess I just won't use gem.bat anymore. Sorry to bother you :D
Reply
Parent - By jlnr (dev) Date 2014-09-29 03:13
wat :) I think I don't even want to understand this bug! Must...not...look...into...
Up Topic Gosu / Gosu News / Gosu 0.8.4 released

Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill