This page describes changes to the 4.4.1 build system.
The build system was replaced for Qt Extended 4.4.1. Please see the Introduction to QBuild for information about the new system.
-edition is no longer supported. Instead, there is the -ui-type switch to select the user interface. -ui-type is a mandatory switch (there is no default value).
All configure options default to off. However, there is now a default device (devices/reference) that turns everything on so that running configure without options will give you a fully-loaded build.
There is a new -modules switch for selecting the modules to build. See Qt Extended Modules.
Features that are tied to modules no longer have switches. You need to turn the modules on instead. The configure Options lists these modules.
If you do not specify a -device, the reference device (devices/reference) is automatically used. This device turns on all features and modules.
There is better support for QVFb builds of device profiles. This is achieved via the -qvfb switch. See QVFb Builds for more information.
There is a new -allow-fail switch that devices can use to allow certain features to be missing when doing a QVFb build.
For every multi-value configure option (eg. -option var,var) there is a -add[-option] and -remove[-option] variant to add or remove an item from the list.
For every list configure option (eg. -option foo -option bar) there is a -no[-option] variant to remove a value from the list.
Devices can place configure switches common to a real and QVFb build in configure-common to avoid duplication. The device-specific values then go into configure while configure-qvfb is used for QVFb.
The link_test is now mandatory for all projects.
Some aspects of the build system have become more automatic (eg. header installation, dependency handling). See Porting to QBuild for more information.
Build system features have become opt-in instead of opt-out. See Porting to QBuild for more information.
The SDK is created incrementally, with SDK contents being stored only in the SDK (and not in the build tree). The SDK now has a default location of <build>/sdk.
Known Issues
A standalone SDK cannot be created. The SDK will work as long as the build and source trees are available.
Most projects in Qtopia do not resemble fully-ported applications (as described in Porting to QBuild). This is due to the maintenance of multiple build systems during the 4.4.1 development phase. These are expected to be cleaned up in a future release.
Building for an x86_64 target does not work.
QBuild bootstrapping requires Qt 4.3 or higher to be installed on the system.
