On Jan 29, 2014, at 11:36 AM, Bradley O'Hearne <br...@bighillsoftware.com> wrote:
> Hello, > > I am working on an app which for the present version, must be installed via > an installer package. The next version will be a Mac App Store app, so this > won’t be a concern then. But for the time being, the app has its own package > installer. > > In Xcode (current version), when you create and distribute an archive, and > attempt to export the option for “Mac Installer Package” it creates an > installer package that we need to customize. Presently we are using the > sorely outdated and deprecated PackageMaker app which came with auxiliary > tools several Xcode versions ago. Aside from the obvious reasons this is > undesirable, it makes building a two-step process where it only need be one, > and also has presented some signing issues in the past. > > What I am trying to accomplish is being able to customize the installer with > some simple branding and addition of a few extra files which need to be > installed, and I would like do drive it all from Xcode, such that exporting > the “Mac Installer Package” in the UI creates this custom installer — I don’t > know if there’s a way to have that process hook a config file, or something > like that, but that’s the idea. > > Can this be done, and if so, can someone point me in the right direction? Have a look at the pkgbuild(1) and productbuild(1) command line tools, and see if they are capable of building a package which is customized to your specifications. If so, you can put the appropriate invocations into your build scripts. Charles _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
