- Qt mac os version mac os x#
- Qt mac os version install#
- Qt mac os version 64 Bit#
- Qt mac os version upgrade#
If you want to follow this advice, there is only one choice, 64-bit Cocoa. 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.
Qt mac os version mac os x#
If your needs fall in between, you can go with a 64-bit Cocoa and 32-bit Carbon universal application.įor Mac OS X 10.6, Apple has started recommending developers to build their applications 64-bit. If you 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 application can target 10.5 and up, then we recommend using Cocoa. Probably the easiest way to determine is to look at the version of Mac OS X you are targetting. Which One Should I Use?Ĭarbon and Cocoa both have their advantages and disadvantages. Note that building for ppc-64 is not supported on 10.6. The following table summarizes the different versions of Mac OS X and what capabilities are used by Qt. Though they may work, We do not support custom-built GCC's. LLVM-GCC support is available by passing in the -platform macx-llvm flag. 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. You can specify alternate compilers though.
Qt mac os version 64 Bit#
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.
Qt mac os version install#
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. Mac OS X is a UNIX platform and behaves similar to other Unix-like platforms. Note that I've commented out the default QMAKE_MACOSX_DEPLOYMENT_TARGET version providing with the Qt install.įinally, you can also specify which sdk to use in your. The file is located in the Qt installation directory at Qt/5.3/clang_64/mkspecs/macx-clang/nfĬONFIG += app_bundle incremental global_init_link_order lib_version_first plugin_no_soname You can change the minimal Mac OS X target by updating the nf file for clang in your Qt installation (I am using Qt5.3).
Qt mac os version upgrade#
OK found the solution after having looked at a similar question: QtCreator build system is broken after OSX upgrade
0 kommentar(er)
