From: Jonathan P. <jp...@dc...> - 2005-06-01 15:13:39
|
On 1 Jun 2005, at 15:54, FUJIMOTO Hisa wrote: > > 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 for the info. Thinking about it further, I realise my question was more like this: I know that during the build process the installed AppKit header files are parsed to generate wrappers. Will the built RubyCocoa be susceptible to (Cocoa, not Ruby) link failures on 10.3 if compiled on Tiger? If so, is there a way to persuade it to build against the 10.3.9 SDK? Thanks. Jonathan |