Qtopia Home - Classes - Hierachy - Annotated - Functions - Qt Embedded

Setting up the Build Environment

• Environment Variables
• Creating the Custom Configuration Files
  • Qt/Embedded
  • tmake
  • qmake
• Acceptable Directory Characters
  • Regular Expression Characters
  • Spaces

Environment Variables

Building Qtopia applications on a target system requires environment variables such as QTDIR to be set. If there is a requirement to use different versions of Qt, the environment variables point to the relevant library configurations.

One method to set the environment variables is to store the settings in a file and enable them by running the source command.

For example, when using Linux (default bash shell) the file could contain the following values:

$ cat qtopia
export QPEDIR=/opt/Qtopia
export QTDIR=/opt/Qtopia
export PATH=$QTDIR/bin:$PATH
export TMAKEPATH=/opt/Qtopia/tmake/lib/qws/linux-generic-g++
export LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH

The environment variables can be enabled quickly via an alias in the .bashrc file.

The following example assumes that the environment settings file is placed in a bin directory within the home directory:

alias qtopia='source ~/bin/qtopia'

Creating the Custom Configuration Files

Building a complete Qtopia system requires three separate configuration systems as follows:

• Qt/Embedded configuration system.
• tmake - used to build Qtopia 1.x, some Qt utilities and some third-party software.
• qmake - used to build Qtopia 2 and above.

Prior to building Qtopia the configuration files must be setup.

The following is an example to create a "myarm" configuration:

cp -r $TMAKEDIR/lib/qws/linux-arm-g++ $TMAKEDIR/lib/qws/linux-myarm-g++
cp -r $QTEDIR/configs/linux-arm-g++-shared $QTEDIR/configs/linux-myarm-g++-shared
cp -r $QPEDIR/mkspecs/qws/linux-arm-g++ $QPEDIR/mkspecs/qws/linux-myarm-g++

Qt/Embedded

Open $QTEDIR/configs/linux-myarm-g++-shared and ensure that the utilities and flags are suitable for the system. For example:

• SYSCONF_CXX, SYSCONF_CC and SYSCONF_LINK might need to be changed to run the correct compiler.
• The option -DMYARM may be added to the compiler flags to place device-specific code inside an #ifdef MYARM

tmake

Open $TMAKEDIR/lib/qws/linux-myarm-g++/tmake.conf and ensure that the utilities and flags are suitable for the system. For example:

• TMAKE_CC, TMAKE_CXX and TMAKE_LINK might need to be changed to run the correct compiler.
• The option -DMYARM may be added to the compiler flags to place device-specific code inside an #ifdef MYARM

qmake

Open $QPEDIR/mkspecs/qws/linux-myarm-g++/qmake.conf and ensure that the utilities and flags are suitable for the system. For example:

• QMAKE_CC, QMAKE_CXX and QMAKE_LINK may need to be changed to run the correct compiler.
• The option -DMYARM may be added to the compiler flags to place device-specific code inside an #ifdef MYARM

Note: The qmake.conf file must have the following code at the bottom of the file:

exists($$(QPEDIR)/src/config.pri):include($$(QPEDIR)/src/config.pri)

Acceptable Directory Characters

Regular Expression Characters

Qtopia 1.9.x and Qtopia 2.0.0 - 2.1.0 have the following character requirements:

• characters in any directory accessed by the Qtopia build system must not contain regular expression characters.
• any special character or character sequence recognised by QRegExp may cause problems.
• the '.' character is accepted as it matches itself.
• regular expression characters in directory names must be avoided. These characters include, but are not limited to: + . ? * \ () [] ^ $ {}.

Note: A patch to remove this limitation exists for Qtopia 2.1.0 and Qtopia 2.1.1 and above do not have this limitation.

Spaces

The Qtopia buildsystem does not support spaces in directory names. This limitation will not fixed in the near future.

Please ensure the following:

• no spaces appear in directory names accessed by the Qtopia build system
• no spaces appear in paths leading to those directories.