The current Mac .app wrapper has a bug that's easy to work around:
Its main binary is three-way universal (Intel 64-bit, 32-bit, PowerPC). But the standard library (or parts of it) are missing the 64-bit component, leading to a crash if you
To discard the 64-bit core and make it a 32-bit app, you can use the following command on the terminal:
lipo -remove x86_64 PATH_TO_YOUR_APP_HERE/Contents/MacOS/RubyGosu\ App -output PATH_TO_YOUR_APP_HERE/Contents/MacOS/RubyGosu\ App
This will be fixed in the next Gosu release.
The only problem with lipo solution is that it seems to break compatibility with the opengl gem. Can't wait for the next version.
Hey there! I know this post is very old, lol, but I see another problem with this App Wrapper:
Some information you might need to know:
My computer - Mac OS X 10.6.8 (Intel 64-bit)
Ruby version - 1.8.7 patch-level 358
I downloaded the wrapper (0.7.47), and when I opened it and it crashed, even if it was just a blank app.
I tried putting a gosu.bundle file in the Resources folder, but nothing got fixed.
Do I need to have a "gosu gem" installed to run it? If so, how can I get it to work without even using the gem?
Process: RubyGosu App 
Path: /Users/taylormcdowell/Desktop/RubyGosu App.app/Contents/MacOS/RubyGosu App
Version: ??? (1.0)
Code Type: X86-64 (Native)
Parent Process: launchd 
Date/Time: 2014-06-04 20:55:22.143 -0400
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 136355 sec
Crashes Since Last Report: 4
Per-App Crashes Since Last Report: 4
Anonymous UUID: A4FEC6BD-2198-4AE7-83C0-4B12A5DB7A31
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
Symbol not found: _environ
Referenced from: /Users/taylormcdowell/Desktop/RubyGosu App.app/Contents/MacOS/../Frameworks/libruby.1.9.1.dylib
Expected in: flat namespace
in /Users/taylormcdowell/Desktop/RubyGosu App.app/Contents/MacOS/../Frameworks/libruby.1.9.1.dylib
From what I remember, that is exactly the bug that I have mentioned in the top posting :)
Er, oops! Sorry, I didn't read your earlier post carefully enough. lol
Thanks anyway. :)
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill