#174: Allow embedding of arbitrary versions of MacRuby
--------------------------------+-------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major | Milestone:
Component: MacRuby | Keywords:
--------------------------------+-------------------------------------------
Comment(by [EMAIL PROTECTED]):
For me the Xcode target has never embedded the metadata. By default it
seems to add itself to the list of targets, there it does nothing I can
observe. If I try and drag it under the Application target itself the
script generates an error because it won't go after the compile sources
build phase.
>I don't think that modifying the BridgeSupport parser to look for
BridgeSupport files inside the framework is a good idea, because it
violates the BridgeSupport load path that we discussed a year ago with the
PyObjC guys.
And then in the very next sentence you say the problem is temporary. So,
given that, why not adopt this approach temporarily? It may not be what
you discussed with the PyObjC folks but it's the best solution for your
users. How are PyObjC even going to know if you add MR itself at the front
of the load path? Why do they care?
m/
--
Ticket URL: <http://www.macruby.org/trac/ticket/174#comment:5>
MacRuby <http://macruby.org/>
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
