Subject:   Installer grief, continued.
Date:   2005-04-28 14:45:35
From:   Snarke
Response to: Installer grief

Didn't work.

I've tried all sorts of things, including the rubycocoa-0.4.1.dmg magic installer program, which (it turns out) is hard-coded to install RubyCocoa into Ruby 1.6.7. Useless for Ruby 1.8.2, as everybody would seem to insist I run.

Anyway, I have confirmed the presense of a /usr/bin/cpp3 file.
> cpp3 --version
cpp3 (GCC) 3.1 20021003 (prerelease)

Now, at this point I really don't know what junk and garbage is still installed where from what, but I started over from the very beginning, in Part I of the article. Used CVS to get a brand-new copy of RubyCocoa-panther (0.4.1, devel-panther, release date of 2003-12-04)

Built, installed, all that jazz. No error messages during Config. During Setup ("building framework target RubyCocoa without using any build style") it appears to have used /usr/bin/gcc-3.3 for compiling. It announced ** BUILD COMPLETED **. Then I find

gcc -fno-common -F../../framework/build -framework RubyCocoa -I. -I/usr/local/lib/ruby/1.8/powerpc-darwin7.5.0 -I/usr/local/lib/ruby/1.8/powerpc-darwin7.5.0 -I/Users/snarke/Personal/Programming/Ruby/rubycocoa-panther/ext/rubycocoa -c -o rubycocoa.o rubycocoa.m
gcc: -framework: linker input file unused because linking not done
gcc: RubyCocoa: linker input file unused because linking not done
cc -dynamic -bundle -undefined suppress -flat_namespace -F../../framework/build -framework RubyCocoa -L"/usr/local/lib" -o rubycocoa.bundle rubycocoa.o -lruby -ldl -lobjc
<--- ext/rubycocoa
<--- ext
install.rb: setup done.

That doesn't look good to me, whatever it means. I run the Install phase, which doesn't generate any errors or warnings that I can see.

I carry on, following the instructions for the RubyCocoaTar app exactly. The paragraph before "Adding The Guts" starts with the sentence "So, you've tried out your new RubyCocoa application and everything seems to be working fine so far, right?"

Alas, no.

[Session started at 2005-04-28 14:28:55 -0700.]
/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/oc_import.rb:22:in `module_eval': undefined method `NSClassFromString' for OSX:Module (NoMethodError)
from /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/oc_import.rb:21:in `module_eval'
from /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/oc_import.rb:21:in `ns_import'
from /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/foundation.rb:5
from /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/cocoa.rb:11:in `require'
from /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/objc/cocoa.rb:11
from /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/cocoa.rb:11:in `require'
from /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/cocoa.rb:11
from /Users/snarke/Personal/Programming/My Programs/My Ruby Programs/RubyCocoaTar/build/ `require'
from /Users/snarke/Personal/Programming/My Programs/My Ruby Programs/RubyCocoaTar/build/

Executable “RubyCocoaTar” has exited with status 1.

Ruby is going to be nearly useless to me if I cannot put a decent interface on it. Sigh. I may have to resort to building AppleScript Studio apps that call Ruby command line modules. How sad is that?