From: Laurent S. <lsa...@ap...> - 2007-10-30 14:49:33
|
This is because you're bundling an extension that was created for Leopard's libruby (1.8.6), and try using it with Tiger's libruby (1.8.2). It's using a symbol that was introduced after, thus the runtime link error. Did you try embedding Leopard's libruby in your application too? Here is a pointer with some details on how to do the trick: http://rubycocoa.sourceforge.net/EmbedRubyCocoa (See Distributing the Ruby Runtime Library). This might work, in Tiger your app would use the embedded version of libruby, and not the system-wide version (in /usr/lib). Laurent On Oct 30, 2007, at 3:41 PM, Rod Schmidt wrote: > I've tried all that. See my message entitled standaloneify on Leopard. > When I run on Tiger I get this: > > Command: PackRat > Path: /Volumes/Internal HD/Users/rod/Development/Projects/ > infiniteNIL/Build/Deployment/PackRat.app/Contents/MacOS/PackRat > Parent: WindowServer [61] > > Version: 1.5 (641M) > > PID: 306 > Thread: Unknown > > Link (dyld) error: > > Symbol not found: _rb_kcode_reset_option > Referenced from: /Volumes/Internal HD/Users/rod/Development/ > Projects/infiniteNIL/Build/Deployment/PackRat.app/Contents/lib/ > strscan.bundle > Expected in: /usr/lib/libruby.1.dylib > > > Rod > > On Oct 30, 2007, at 7:29 AM, Laurent Sansonetti wrote: > >> Hi Rod, >> >> I never tried doing this, which is a shame, but I would start like >> this: >> >> 1) build RubyCocoa with MACOSX_DEPLOYMENT_TARGET=10.4 >> 2) build your app with MACOSX_DEPLOYMENT_TARGET=10.4 and link to the >> new builded RubyCocoa >> 3) embed the new builded RubyCocoa in your app >> >> You might also want to embed libruby too. >> >> There will be a problem with the threading support, which is >> different >> in 10.4 and 10.5. Current RubyCocoa cannot handle both in the same >> binary (we use preprocessor macros to isolate the non-required code), >> we need to fix this so that at runtime RubyCocoa can activate the >> right code path according to the system version. >> >> Laurent >> >> On Oct 30, 2007, at 5:40 AM, Rod Schmidt wrote: >> >>> Is it possible to build a standalone RubyCocoa app on Leopard and >>> have >>> it run in Tiger? In other words, does the RubyCocoa framework >>> support >>> 10.4? >>> >>> Thanks, >>> >>> Rod >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a >>> browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> Rubycocoa-talk mailing list >>> Rub...@li... >>> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a >> browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Rubycocoa-talk mailing list >> Rub...@li... >> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |