[MacRuby-devel] macruby_deploy
The silence is defening! Is anyone able to get a compiled and sandboxed MacRuby project accepted to the App Store? If I understand how macruby_deploy works then it seems that it is trying to duplicate a lot of work that Xcode does by post-processing an Xcode application package. It also seems to me that it would solve my problem it I could include a source code bundle for the macruby runtime in my project so that Xcode would build it correctly with sandboxing enabled. Then I would need an option for macruby_deploy to not overwrite the executable, or, better yet, a macruby pre-compiler that I could invoke from the Xcode "Build Rules". Then I wouldn't need to run macruby_deploy and the build should even run faster since code signing would only run once. So what don't I understand about macruby_deploy? Thanks, Bob Rice ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macruby-devel
Re: [MacRuby-devel] macruby_deploy
Bob, I've deployed to the App Store without issue. Are you using the --embed argument for the Deployment target? dw On Thu, Sep 20, 2012 at 11:47 AM, Robert Carl Rice wrote: > The silence is defening! > > Is anyone able to get a compiled and sandboxed MacRuby project accepted to > the App Store? > > If I understand how macruby_deploy works then it seems that it is trying > to duplicate a lot of work that Xcode does by post-processing an Xcode > application package. It also seems to me that it would solve my problem it > I could include a source code bundle for the macruby runtime in my project > so that Xcode would build it correctly with sandboxing enabled. Then I > would need an option for macruby_deploy to not overwrite the executable, > or, better yet, a macruby pre-compiler that I could invoke from the Xcode > "Build Rules". Then I wouldn't need to run macruby_deploy and the build > should even run faster since code signing would only run once. > > So what don't I understand about macruby_deploy? > > Thanks, > Bob Rice > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo/macruby-devel > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macruby-devel
Re: [MacRuby-devel] macruby_deploy
Hi Daniel: When I use the arguments: --compile --codesign "3rd Party Mac Developer Application: Robert Rice" I get an app bundle that runs and passes validation but then is rejected as an "invalid binary" because the executable doesn't enable sandboxing. When I add the embed argument: --compile --embed --codesign "3rd Party Mac Developer Application: Robert Rice" I get an app bundle that runs but fails validation with the error: “Deployment” does not contain a single–bundle application or contains multiple products. Please select another archive, or adjust your scheme to create a single–bundle application. My app could be submitted for review if I don't compile the ruby source. Thanks, Bob Rice On Sep 20, 2012, at 3:32 PM, Daniel Westendorf wrote: > Bob, > > I've deployed to the App Store without issue. Are you using the --embed > argument for the Deployment target? > > dw > > On Thu, Sep 20, 2012 at 11:47 AM, Robert Carl Rice > wrote: > The silence is defening! > > Is anyone able to get a compiled and sandboxed MacRuby project accepted to > the App Store? > > If I understand how macruby_deploy works then it seems that it is trying to > duplicate a lot of work that Xcode does by post-processing an Xcode > application package. It also seems to me that it would solve my problem it I > could include a source code bundle for the macruby runtime in my project so > that Xcode would build it correctly with sandboxing enabled. Then I would > need an option for macruby_deploy to not overwrite the executable, or, better > yet, a macruby pre-compiler that I could invoke from the Xcode "Build Rules". > Then I wouldn't need to run macruby_deploy and the build should even run > faster since code signing would only run once. > > So what don't I understand about macruby_deploy? > > Thanks, > Bob Rice > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo/macruby-devel > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macruby-devel
Re: [MacRuby-devel] macruby_deploy
Hi guys, I have no bundled anything for the app store myself, but I recall something from earlier this year. The email thread can be found here: http://lists.macosforge.org/pipermail/macruby-devel/2012-June/008841.html HTH, Mark On 2012-09-20, at 3:50 PM, Robert Carl Rice wrote: > Hi Daniel: > > When I use the arguments: > --compile --codesign "3rd Party Mac Developer Application: Robert Rice" > I get an app bundle that runs and passes validation but then is rejected as > an "invalid binary" because the executable doesn't enable sandboxing. > > When I add the embed argument: > --compile --embed --codesign "3rd Party Mac Developer Application: Robert > Rice" > I get an app bundle that runs but fails validation with the error: > “Deployment” does not contain a single–bundle application or contains > multiple products. Please select another archive, or adjust your scheme to > create a single–bundle application. > > My app could be submitted for review if I don't compile the ruby source. > > Thanks, > Bob Rice > > > On Sep 20, 2012, at 3:32 PM, Daniel Westendorf wrote: > >> Bob, >> >> I've deployed to the App Store without issue. Are you using the --embed >> argument for the Deployment target? >> >> dw >> >> On Thu, Sep 20, 2012 at 11:47 AM, Robert Carl Rice >> wrote: >> The silence is defening! >> >> Is anyone able to get a compiled and sandboxed MacRuby project accepted to >> the App Store? >> >> If I understand how macruby_deploy works then it seems that it is trying to >> duplicate a lot of work that Xcode does by post-processing an Xcode >> application package. It also seems to me that it would solve my problem it I >> could include a source code bundle for the macruby runtime in my project so >> that Xcode would build it correctly with sandboxing enabled. Then I would >> need an option for macruby_deploy to not overwrite the executable, or, >> better yet, a macruby pre-compiler that I could invoke from the Xcode "Build >> Rules". Then I wouldn't need to run macruby_deploy and the build should even >> run faster since code signing would only run once. >> >> So what don't I understand about macruby_deploy? >> >> Thanks, >> Bob Rice >> >> ___ >> MacRuby-devel mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo/macruby-devel >> >> ___ >> MacRuby-devel mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo/macruby-devel > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macruby-devel
