Hmm, I'm not sure why this happening, but I can tell you that taking out the Current symlink and not including the headers is something that is explicitly done during the embedding process.
In fact, taking out the Current symlink was done because it was causing App Store validation to fail for someone, there is a comment in the source explaining that. I'm not sure why the headers are not included by default, a dev might be able to answer that question. Mark Rada mr...@marketcircle.com On 2011-04-10, at 9:24 PM, Chris Lloyd wrote: > Hi, > > I'm trying to submit a MacRuby app that I've been working on to the App > Store. I'm using v0.10 and XCode 4. A working binary is produced, however > validation fails because of multiple missing symlinks. This happens even with > an empty app generated from the scaffold. It seems as though there are two > issues: > In the macruby.framework directory there is no "Current" version. Creating a > symlink for this doesn't work as Xcode gets confused with the separate > Info.plist. A workaround I've been using is to rename the "0.10" folder to > "Current". > None of the Headers are copied in. > Am I doing something wrong? This seems like something that somebody must have > stumbled into before. > > Cheers, > > Chris Lloyd > > > PS. It would be kick-ass if ruby_deploy supported Bundler for getting a list > of Gems to include. `macruby_deploy --compile --embed --bundle` > > _______________________________________________ > 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
