#packagemaker

This post will show you how to create the simplest possible installer package with pkgbuild.

Making a simple installer is actually easy, but Apple only provides us with a man page and most tutorials dive too deep straight away.

That's not great. It's an intimidating tool. Let's start with the basics.

How to: Making OS X Installer Packages like a Pro – Xcode4 Developer ID Mountain Lion ready pkg

Making OS X Installer Packages like a Pro – Xcode4 Developer ID Mountain Lion ready pkg

Note: This is for OS X Installer packages only, packages for submission to the Mac App Store follow different rules.

Because of Mountain Lions Gatekeeper I finally had to take my PackageMakerbuild script behind the barn and shoot it. PackageMaker was already removed from Xcode and moved into “Auxiliary Tools…

Just a quick list for anybody who happen to come across same issues as me. If you have built an app and for some Godforsaken reason had to use PackageMaker following are things to watch out when moving your project to XCode 4 / Lion. (Yes you read correct, if you do not have to please please do not use PackageMaker, even Apple does not use it themselves)

XCode 4 output directory is now in Library

Not just that it builds your product in ~/Library it also creates a folder consisting of your productname-some_random_characters. Trouble with the folders in ~/Library is that these are not selectable in folder browser from PackageMaker (or elsewhere). It is also not guarenteed to work if you copy paste the complete path from Terminal. Copying the product does not copy everything needed and will fail the installer build as well. There are two ways to change build location:

XCode > Preferences > Locations (Change the default to Relative for a subfolder in workspace or Change to custom for a custom location) - this change is global and recommended.

File > Project Settings > Build (similar changes as above) - this change is per project basis.

Double check location of resources and images

PackageMaker will not always give a helpful error if you have changed your core path of resources and product. Make sure you check path on everything including but not limited to Interface Editor - Background, app (as explained in first step), any other files and scripts.

Triple check location of scripts / jump into XML