That’s no good. Can you file a ticket? (Preferably with the test framework 
attached)

On Nov 17, 2010, at 3:34 PM, Alan Skipp wrote:

> Thanks for the reply. I have the bridgesupport file located in the 
> '/Resources/BridgeSupport/' folder of the framework, but currently it is not 
> automatically loaded. I've tried making a clean build to no avail and I've 
> checked the built app package and the framework is copied and the 
> bridgesupport file is present. I also created a new test project in Xcode 
> (just in case something had went awry with the other project) and I had to 
> explicitly call 'load_bridge_support_file' to get the framework working there 
> also.
> 
> 
> On 17 Nov 2010, at 13:42, Eloy Duran wrote:
> 
>> The BridgeSupport file should be in a BridgeSupport directory inside the 
>> framework’s Resources directory. For example, Foundation’s BridgeSupport 
>> file is at: 
>> /System/Library/Frameworks/Foundation.framework/Resources/BridgeSupport/Foundation.bridgesupport
>> 
>> On Nov 17, 2010, at 2:32 PM, Alan Skipp wrote:
>> 
>>> Thanks for the info. I'd wrongly assumed that as blocks can be treated as 
>>> Objective-C objects that I could just go ahead and use them in Macruby.
>>> I have it working now, which is great, though I do have one more question. 
>>> Initially I was receiving the same errors after I'd included the framework 
>>> with a bridgesupport file into my project. I finally got it working after 
>>> invoking, 'load_bridge_support_file' in my controller class. Is there 
>>> something I should be doing that would enable macruby to automatically 
>>> detect and load the bridgesupport file included in my framework?
>>> 
>>> Cheers,
>>> Al
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Reply via email to