#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]):
I've been having a lot of problems with this. I can't make the Xcode
target work at all and, because of a confusion, I managed to release a
version update without the bridge support metadata and am getting crash
reports. I think this process is brittle and introduces unnecessary
dependencies into my project not to mention adding several seconds to each
build cycle (whether needed or not and they do add up).
I would like, instead, to see the MacRuby build process (perhaps governed
by some kind of flag) embed the bridge support metadata into the
MacRuby.framework bundle itself and look for them there first. This would
eliminate any dependency in my application project and allow me to treat
MacRuby.framework as I would any other framework (which is a very good
thing). It would also considerably reduce the change that I will ever
again release a binary without the patched metadata.
I took a look at bs.c but, although the relevant area is obvious enough to
spot, I would not be confident to make this change myself. The "Ruby C"
coding style is not for the faint hearted.
Matt
--
Ticket URL: <http://www.macruby.org/trac/ticket/174#comment:3>
MacRuby <http://macruby.org/>
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
