Pierce T. Wetter III
pierc****@twinf*****
Sat Apr 21 02:14:52 JST 2007
On Apr 20, 2007, at 9:58 AM, Laurent Sansonetti wrote: > > On Apr 20, 2007, at 6:11 PM, Pierce T. Wetter III wrote: >> On Apr 20, 2007, at 8:28 AM, Laurent Sansonetti wrote: >>> Sorry for the long reply (I have been away for the week). I will >>> also >>> reply to your CoreData thread. >>> >>> Regarding this issue, it is unfortunately not possible yet to embed >>> RubyCocoa, as it requires it to locate the bridge support files. We >>> will make sure the next release will support this though. >> >> Ah, that was all the hint I needed. >> >> Looking at the code, it already looks in RubyCocoa.framework/ >> Resources for the BridgeSupport folder, so copying /Library/ >> BridgeSupport into there in the build after the fact works. > > Ah true, Hisa-san added that recently :-) I think that RubyCocoa will > also look in YourApp.app/Resources/BridgeSupport. Nope, tried that first. :-) > >> So probably this could be done via a project file tweak. Make a >> second xcode project called RC embeddable that has the standard >> configurations (Debug/Release), includes the regular framework, and >> copies the BuildSupport files into the framework. > > Mmh nice idea. Maybe an Xcode target might be preferable there (so you > could just keep your existing application project and add the target). If you do the thing where you drag the RubyCocoa project into your project, it will build RubyCocoa with the configuration of the same name as your project. Since RubyCocoa is setup for Development/ Deployment while most apps are setup for Debug/Release, a "Release" configuration that added/built the BridgeSupport files would work "automagically". Pierce
