|  | Home · All Classes · All Functions · Overviews

# Developing Qt Applications on Mac OS X

- What Versions of Mac OS X are Supported?

- Carbon or Cocoa?
- Which One Should I Use?

- Universal Binaries
- Day-to-Day Application Development on OS X
- Deployment - "Compile once, deploy everywhere"

Mac OS X is a UNIX platform and behaves similar to other Unix-like platforms. The main difference is X11 is not used as the primary windowing system. Instead, Mac OS X uses its own native windowing system that is accessible through the Carbon and Cocoa APIs. Application development on Mac OS X is done using Xcode Tools, an optional install included on every Mac with updates available from Apple's developer website. Xcode Tools includes Apple-modified versions of the GCC compiler.

### What Versions of Mac OS X are Supported?

As of Qt 4.6, Qt supports Mac OS X versions 10.4 and up. It is usually in the best interest of the developer and user to be running the latest updates to any version. We test internally against Mac OS X 10.4.11 as well as the updated release of Mac OS X 10.5 and Mac OS X 10.6.

#### Carbon or Cocoa?

Historically, Qt has used the Carbon toolkit, which supports 32-bit applications on Mac OS X 10.4 and up. Qt 4.5 and up has support for the Cocoa toolkit, which requires 10.5 and provides 64-bit support.

This detail is typically not important to Qt application developers. Qt is cross-platform across Carbon and Cocoa, and Qt applications behave the same way when configured for either one. Eventually, the Carbon version will be discontinued. This is something to keep in mind when you consider writing code directly against native APIs.

The current binary for Qt is built in two flavors, 32-bit Carbon and full universal Cocoa (32-bit and 64-bit). If you want a different setup for Qt will use, you must build from scratch. Carbon or Cocoa is chosen when configuring the package for building. The configure process selects Carbon by default, to specify Cocoa use the `-cocoa` flag. configure for a 64-bit architecture using one of the `-arch` flags (see Universal Binaries).

Currently, Apple's default GCC compiler is used by default (GCC 4.0.1 on 10.4 and 10.5, GCC 4.2 on 10.6). You can specify alternate compilers though. For example, on Mac OS X 10.5, Apple's GCC 4.2 is also available and selectable with the configure flag: `-platform macx-g++42`. LLVM-GCC support is available by passing in the `-platform macx-llvm` flag. GCC 3.x will not work. Though they may work, We do not support custom-built GCC's.

The following table summarizes the different versions of Mac OS X and what capabilities are used by Qt.

Mac OS X Version | Cat Name | Native API Used by Qt | Bits available to address memory | CPU Architecture Supported | Development Platform
--- | --- | --- | --- | --- | ---
10.4 | Tiger | Carbon | 32 | PPC/Intel | Yes
10.5 | Leopard | Carbon | 32 | PPC/Intel | Yes
10.5 | Leopard | Cocoa | 32/64 | PPC/Intel | Yes
10.6 | Snow Leopard | Cocoa/Carbon | 32 | PPC/Intel | Yes
10.6 | Snow Leopard | Cocoa | 64 | Intel | Yes

Note that building for ppc-64 is not supported on 10.6.

#### Which One Should I Use?

Carbon and Cocoa both have their advantages and disadvantages. Probably the easiest way to determine is to look at the version of Mac OS X you are targetting. If you are starting a new application and can target 10.5 and up, then please consider Cocoa only. If you have an existing application or need to target earlier versions of the operating system and do not need access to 64-bit or newer Apple technologies, then Carbon is a good fit. If your needs fall in between, you can go with a 64-bit Cocoa and 32-bit Carbon universal application with the appropriate checks in your code to choose the right path based on where you are running the application.

For Mac OS X 10.6, Apple has started recommending developers to build their applications 64-bit. The main reason is that there is a small speed increase due to the extra registers on Intel CPU's, all their machine offerings have been 64-bit since 2007, and there is a cost for reading all the 32-bit libraries into memory if everything else is 64-bit. If you want to follow this advice, there is only one choice, 64-bit Cocoa.

### Universal Binaries

In 2006, Apple begin transitioning from PowerPC (PPC) to Intel (x86) systems. Both architectures are supported by Qt. The release of Mac OS X 10.5 in October 2007 added the possibility of writing and deploying 64-bit GUI applications. Qt 4.5 and up supports both the 32-bit (PPC and x86) and 64-bit (PPC64 and x86-64) versions of PowerPC and Intel-based systems.

Universal binaries are used to bundle binaries for more than one architecture into a single package, simplifying deployment and distribution. When running an application the operating system will select the most appropriate architecture. Universal binaries support the following architectures; they can be added to the build at configure time using the `-arch` arguments:

Architecture | Flag
--- | ---
Intel, 32-bit | `-arch x86`
Intel, 64-bit | `-arch x86_64`
PPC, 32-bit | `-arch ppc`
PPC, 64-bit | `-arch ppc64`

If there are no `-arch` flags specified, configure builds for the 32-bit architecture, if you are currently on one. Universal binaries were initially used to simplify the PPC to Intel migration. You can use `-universal` to build for both the 32-bit Intel and PPC architectures.

Note: The `-arch` flags at configure time only affect how Qt is built. Applications are by default built for the 32-bit architecture you are currently on. To build a universal binary, add the architectures to the CONFIG variable in the .pro file:

     CONFIG += x86 ppc x86_64 ppc64

### Day-to-Day Application Development on OS X

On the command-line, applications can be built using `qmake` and `make`. Optionally, `qmake` can generate project files for Xcode with `-spec macx-xcode`. If you are using the binary package, `qmake` generates Xcode projects by default; use `-spec macx-gcc` to generate makefiles.

The result of the build process is an application bundle, which is a directory structure that contains the actual application executable. The application can be launched by double-clicking it in Finder, or by referring directly to its executable from the command line, i. e. `myApp.app/Contents/MacOS/myApp`.

If you wish to have a command-line tool that does not use the GUI (e.g., `moc`, `uic` or `ls`), you can tell `qmake` not to execute the bundle creating steps by removing it from the `CONFIG` in your `.pro` file:

     CONFIG -= app_bundle

### Deployment - "Compile once, deploy everywhere"

In general, Qt supports building on one Mac OS X version and deploying on all others, both forward and backwards. You can build on 10.4 Tiger and run the same binary on 10.5 and up.

Some restrictions apply:

- Some functions and optimization paths that exist in later versions of Mac OS X will not be available if you build on an earlier version of Mac OS X.
- The CPU architecture should match.
- Cocoa support is only available for Mac OS X 10.5 and up.

Universal binaries can be used to provide a smorgasbord of configurations catering to all possible architectures.

Mac applications are typically deployed as self-contained application bundles. The application bundle contains the application executable as well as dependencies such as the Qt libraries, plugins, translations and other resources you may need. Third party libraries like Qt are normally not installed system-wide; each application provides its own copy.

The most common way to distribute applications is to provide a compressed disk image (.dmg file) that the user can mount in Finder. The Mac deployment tool (macdeployqt) can be used to create the self-contained bundles, and optionally also create a .dmg archive. See the Mac deployment guide for more information about deployment. It is also possible to use an installer wizard. More information on this option can be found in Apple's documentation.