Documentation :: Compiling Sequel Pro

Under Development


Compiling Sequel Pro for yourself is a fairly easy process. We use the standard Cocoa toolchain, based around Xcode, with one or two complications due to the libraries used.

Getting the Sequel Pro source

The Sequel Pro source is currently hosted on Google Code - a web interface is available via the Google code project page, and the Source checkout page provides instructions on how to retrieve the latest source via svn.

Once you have a local copy of the source on your machine, open the "sequel-pro.xcodeproj" Xcode project file to browse and compile the Sequel Pro source within Xcode.

Compiling the Sequel Pro source

The first time you try to build the downloaded project, you will probably see an error trying to compile the "nibs"/"xibs" - the interface component references. This is because we use additional libraries to build the interface, in particular BWToolkit from Brandon Walkin.

To compile the interface files, you'll need to download the BWToolkit Interface Builder Plugin, and add it to Interface Builder (usually as easy as double-clicking the downloaded .ibplugin file).

Code Signing

If you're making a number of changes, or keeping your local copy of the source up to date with the trunk, you may be prompted for Keychain access to your passwords every time you launch a new copy in 10.6+. This can be very frustrating, but there is a solution: code signing. By signing each build with a private key, the keychain records that applications signed with that key all have access to the same passwords, so you are no longer prompted with each new compile.

The "Debug" build phase is set to look for a code signing key named "Sequel Pro Development" in your keychain. To create this key in Snow Leopard, follow these steps:

  • Launch "Keychain Access", located in your /Applications/Utilities/ folder.
  • Go to the "Keychain Access" menu, into the "Certificate Assistant" submenu, and choose "Create a Certificate…"
  • Enter "Sequel Pro Development" in the name field
  • Select "Code Signing" as the Certificate Type
  • Click on the "Continue" button, confirm the prompt, and click on "Done".

The next time you build the project in Debug mode, you will be asked to confirm code signing by Keychain Access - select Allow Always to no longer be shown the prompt. You will have to confirm keychain access to passwords one last time.