From: FUJIMOTO H. <hi...@fo...> - 2005-06-01 14:54:32
|
At Wed, 1 Jun 2005 13:51:18 +0100, Jonathan Paisley wrote: > On 1 Jun 2005, at 13:33, FUJIMOTO Hisa wrote: > > > RubyCocoa 0.4.1 binary package (dmg) for Tiger (Mac OS X 10.4) is > > here: > > > > http://prdownloads.sourceforge.net/rubycocoa/RubyCocoa-0.4.1- > > tiger.dmg > > > > What will happen if this framework is used on Panther? Rubycocoa of the current Tiger binary package is (dynamic) linked to /usr/lib/libruby.dylib. So it may be depend on /usr/lib/libruby.dylib on target environment: $ cd /tmp && mkdir foo && cd foo $ gzcat /Volumes/RubyCocoa-0.4.1-tiger/RubyCocoa-0.4.1.pkg/Contents/Archive.pax.gz | \ pax -r ./Library/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa $ otool -L ./Library/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa ./Library/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa: @executable_path/../Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa \ (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa \ (compatibility version 1.0.0, current version 11.0.0) /usr/lib/libruby.1.dylib (compatibility version 1.8.0, current version 1.8.2) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.0.0) It's difficult to decide which (and how) libruby is linked for *binary package* when different requirement exists. It may be better that you build rubycocoa by yourself tuned for your purpose. thanks, -- FUJIMOTO Hisa |