For the Cocoa version, 64 bit is chosen by default.Ĭurrently, 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). To explicitly configure Qt to build for 34-bit or 64-bit architectures (or both), use the -arch flags (see Universal Binaries).
If you want a different setup you must build Qt yourself using the source package. There are two versions of the Qt binary, one with x86 and x86_64 Cocoa and another with x86 and ppc Carbon. To build Qt for Carbon, specify the -carbon flag to configure. Qt uses Cocoa by default, both for the binary package and when configuring Qt from source (using the configure script). With Qt 4.7 we recommend using the Cocoa version of Qt for development, unless you want to target the 10.4 platform. Note: There is no accessibility support in the Cocoa version. With Carbon, Qt can be developed on and deployed to 10.4, but there is no 64-bit support. Using the Cocoa API, Qt requires 10.5 and provides both 32-bit and 64-bit support.
Qt supports building in two flavors, using either the Carbon or Cocoa API.
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. It is usually in the best interest of the developer and user to be running the latest updates to any version. What Versions of Mac OS X are Supported?Īs of Qt 4.7, Qt supports Mac OS X versions 10.4 and up. Xcode Tools includes Apple-modified versions of the GCC compiler.
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. Instead, Mac OS X uses its own native windowing system that is accessible through the Carbon and Cocoa APIs. The main difference is X11 is not used as the primary windowing system. Hopefully I won’t have to do another major upgrade of macOS any time soon (I may buy a new Mac next time).Mac OS X is a UNIX platform and behaves similar to other Unix-like platforms. I guess I will use it from my macOS 10.14 laptop and then eventually do the tedious job of porting those websites to Jekyll. If so they should really take down the Hammer4Mac website. It starts, but returns ‘Build failed’ for all 3 websites. Hammer4Mac is a static website builder I use to build the PerfectTablePlan website and a couple of other mini sites. But I only use the compiler from the command line via QtCreator, so it doesn’t really matter at present. It says that it requires additional components and then fails to install them. XCode 10.1 falls over if I try to start it. So far I haven’t been able to get the following to work: The Subversion command line no longer worked from the terminal, but that was easily fixed by adding /Applications/XCode.app/Developer/usr/bin to PATH in my. Even more annoyingly the upgrade costs nearly as much as a new licence, which feels predatory.
I had to update some of the software I use:Īnnoyingly, I had to buy an upgrade of SnagIt as the 2018 version doesn’t work on Big Sur. I was then able to rebuild my Qt-based products: Easy Data Transform, PerfectTablePlan and Hyper Plan using the existing installs of Qt 5.13.1 and Qt Creator 4.8.0. After a bit a Googling I managed to find this magic incantation to type into the terminal on a forum post: defaults write .Xcode DVTDisableMainThreadChecker 1 A glance at Activity Monitor showed that several XCode related processes were going crazy. But when I tried to run Qt Creator the CPU shot to 99% and stayed there, making the machine unusable. The initial upgrade of OS was straightforward enough. However glitches had been reported in Easy Data Transform on macOS 11.0 (Big Sur) and I wasn’t ready to abandon my 2017 iMac, so I decided to bite the bullet and upgrade it from macOS 10.13 to 11.0. On Windows I generally buy a new PC rather than upgrade OS. So I try to do it as infrequently as I can get away with. It is always a bit of fraught process upgrading a computer OS, especially for a development machine with loads of tools and libraries installed.