From james at dieneuemodern.com Sat Nov 3 13:50:38 2007 From: james at dieneuemodern.com (James Hicks) Date: Sat, 3 Nov 2007 17:50:38 +0000 Subject: [Rubyosa-discuss] Install failed on Leopard Message-ID: <1021A755-2C53-4203-865E-62B9F01B0AE6@dieneuemodern.com> I just tried to install Rubyosa on a clean Leopard install (excluding dev tools and X11) Of course typing "sudo gem install rubyosa" into the Terminal and this is the error I received: ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError) ERROR: Failed to build gem native extension. ruby extconf.rb install rubyosa can't find header files for ruby. Anyone got any ideas? Thanks! From jmacaulay at gmail.com Sat Nov 3 14:13:01 2007 From: jmacaulay at gmail.com (James MacAulay) Date: Sat, 3 Nov 2007 14:13:01 -0400 Subject: [Rubyosa-discuss] Install failed on Leopard In-Reply-To: <1021A755-2C53-4203-865E-62B9F01B0AE6@dieneuemodern.com> References: <1021A755-2C53-4203-865E-62B9F01B0AE6@dieneuemodern.com> Message-ID: <4D859541-D4CD-4041-B15E-F1D9140D46D0@gmail.com> Looks like maybe you do need the dev tools installed, if it is complaining about not being able to build a native extension. Seems like it needs gcc. (?) James On 3-Nov-07, at 1:50 PM | Nov 3, James Hicks wrote: > I just tried to install Rubyosa on a clean Leopard install (excluding > dev tools and X11) > > Of course typing "sudo gem install rubyosa" into the Terminal and this > is the error I received: > > ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError) > ERROR: Failed to build gem native extension. > > ruby extconf.rb install rubyosa > can't find header files for ruby. > > > Anyone got any ideas? > > Thanks! > _______________________________________________ > Rubyosa-discuss mailing list > Rubyosa-discuss at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyosa-discuss From mac at casteel.org Tue Nov 13 18:59:11 2007 From: mac at casteel.org (Michael Casteel) Date: Tue, 13 Nov 2007 15:59:11 -0800 Subject: [Rubyosa-discuss] Leopard variation Message-ID: I got RubyOSA working with the Leopard Ruby install, and my app (developed on Tiger) pretty much works, but something is different. One of the apps I'm scripting is iRed, an infrared controller app, which I use to send IR codes to audio equipment. The problem I'm seeing is that the iRed vocabulary in RubyOSA is different under Leopard than under Tiger. The specific problem I see is with the 'send2' method as implemented by rbosa. Under Tiger, this method takes one argument, per rdoc-osa: send2(ir) Send the IR code. ir: Which code? After running rdoc-osa under Leopard, I see: send2(direct, ir) Send the IR code. direct: The object for the command. ir: Which code? Interestingly, the documented hierarchy differs as well, i.e. the send2 command was documented under OSA::iRed::Item, but now it's under OSA::IRed::Application. In both Tiger and Leopard, ::Application's parent is ::Item. BTW, in Script Editor this command appears as 'send' instead of 'send2'. At least I think that's the command, I don't see any 'send2' when I open the dictionary with Script Editor. When I have time, I'll move the IR transmitter to the Leopard machine and try to get the code working on Leopard, but I'm not confident that I'll be able to create Ruby code that's portable between Tiger and Leopard because of these differences. It would be nice to have a compatible option (unlike Apple's scripting bridge which is Leopard-only). The other app I'm scripting here is iTunes, which had one command (reveal) move levels; I originally called it at the application level, but that isn't there in Leopard. Calling it at the playlist level works on both Leopard and Tiger, though, so no real problem there. -- Mike Casteel Seattle, WA