kimura wataru
kimur****@i*****
Thu Aug 31 00:17:57 JST 2006
On Sun, 27 Aug 2006 22:09:07 +0100, Jonathan Paisley wrote: > > On 25 Aug 2006, at 15:44, kimura wataru wrote: > >> I wrote a patch to fix a RubyCocoa (svn trunk) crash on ruby without >> '--enable-shared' option. The old .pbproj has a setting >> "SINGLE_MODULE = NO" >> to disable a linker option "-Wl,-single_module". RubyCocoa linking >> libruby.a built with the linker option did not work correctly. > > Under what circumstances is it useful to link statically? I think > perhaps it's better to link dynamically to libruby.dylib to make it > clear what the dependencies are. > I agree that dynamic linking has some advantages. But to enable to build with static library will avoid problems from missing ruby's --enable-shared option. I think there is no reason not to support static linking, because we can solve that with only to set an option at this time. In the future, if RubyCocoa requires dynamic linking from technical reasons then the config step should fail with an error. >> Now, the repository of RubyCocoa project is moving to macosforge >> ([Rubycocoa-devel:372]). Is it better not to commit to the repository >> in sourceforge? > > It's probably better to wait. However, it should be fairly easy to > merge any changes made to the sourceforge repository, once the > macosforge repository is available. > Thanks, I'll wait. -- kimura wataru
