Hiya,
As someone experiencing this discussion from the 3rd person
perspective, I'd like to chime in.
The current issue seems to be that there are some problems with the
current MR,
which will get properly fixed by a future software update.
Until then there apparently is the need to work around this in
different ways.
Laurent added his, but it broke Matts existing one.
So my question to Laurent is, since it's _all_ suboptimal atm, would
it be possible to re-enable
the BUILD_AS_EMBEDDABLE option so everyone can go on without wasting
time on a tmp workaround?
Cheers,
Eloy "always in for a discussion" Duran ;-)
On 9 dec 2008, at 16:18, Matt Mower wrote:
On Mon, Dec 8, 2008 at 10:51 AM, MacRuby <ruby-
[EMAIL PROTECTED]> wrote:
Replying to [comment:7 [EMAIL PROTECTED]:
Did you verify with {{{otool(1)}}} that your binary links against
the
version of MacRuby inside the bundle?
As far as I understand it there are two issues:
1) broken BS metadata
2) where does MacRuby get looked for
As of a couple of (MacRuby) builds ago I had no problem with either. I
had a run script phase in my existing target (using Laurents script)
to embed the right metadata.
I note that Laurent created an Xcode target for MacRuby but it doesn't
fit into my build workflow and, therefore, I don't want to use it.
I would like the BUILD_AS_EMBEDDABLE option back and to be able to
manage MacRuby.framework myself as I would any other framework.
Regards,
Matt
--
Matt Mower :: http://matt.blogs.it/
_______________________________________________
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
