安装 PyQt4 ¶

使用 configure-ng.py ¶

configure-ng.py script is used to configure PyQt4 as follows:

python configure-ng.py
									

This assumes that the Python interpreter is on your path. Something like the following may be appropriate on Windows:

c:\python34\python configure-ng.py
									

If you have multiple versions of Python installed then make sure you use the interpreter for which you wish to build PyQt4 for.

The full set of command line options is:

--assume-shared ¶

Normally Qt is checked to see if it has been built as shared libraries. Some Linux distributions configure their Qt builds to make this check unreliable. This option ignores the result of the check and assumes that Qt has been built as shared libraries.

--bindir <DIR> , -b <DIR> ¶

pyuic4 , pyrcc4 and pylupdate4 utilities will be installed in the directory <DIR> .

--concatenate , -c ¶

The C++ source files for a Python module will be concatenated. This results in significantly reduced compilation times. Most, but not all, C++ compilers can handle the large files that result. See also the --concatenate-split 选项。

--concatenate-split <N> , -j <N> ¶

若 --concatenate option is used to concatenate the C++ source files then this option determines how many files are created. The default is 1.

--configuration <FILE> ¶

<FILE> contains the configuration of the PyQt4 build to be used instead of dynamically introspecting the system and is typically used when cross-compiling. See 采用配置文件进行配置 .

--confirm-license ¶

Using this confirms that you accept the terms of the PyQt4 license.

--dbus <DIR> , -s <DIR> ¶

dbus-python.h header file of the dbus-python package can be found in the directory <DIR>/dbus .

--debug , -u ¶

The PyQt4 modules will be built with debugging symbols. On Windows this requires that a debug version of Python is installed.

--designer-plugindir <DIR> ¶

The Python plugin for Qt Designer will be installed in the directory <DIR> .

--destdir <DIR> , -d <DIR> ¶

The PyQt4 Python package will be installed in the directory <DIR> . The default is the Python installation's site-packages directory. If you use this option then the PYTHONPATH environment variable must include <DIR> .

--enable <MODULE> , -e <MODULE> ¶

Normally all PyQt4 modules are enabled and are built if the corresponding Qt library can be found. Using this option only those modules specifically enabled will be checked for and built. The option may be specified any number of times.

--help , -h ¶

Display a help message.

--license-dir <DIR> ¶

The license files needed by the commercial version of PyQt4 can be found in the directory <DIR> .

--no-deprecated ¶

All Qt v4 features that have been deprecated in Qt v5 will be disabled. This is useful when porting PyQt4 applications to PyQt5.

--no-designer-plugin ¶

The Qt Designer plugin will not be built.

--no-docstrings ¶

The PyQt4 modules will not contain automatically generated docstrings.

--no-python-dbus ¶

The Qt support for the standard Python DBus bindings is disabled.

--no-qsci-api ¶

PyQt4.api QScintilla API file is not installed even if QScintilla does appear to be installed.

--no-sip-files ¶

.sip files for the PyQt4 modules will not be installed.

--no-tools ¶

New in version 4.11.

pyuic4 , pyrcc4 and pylupdate4 tools will not be built.

--no-timestamp , -T ¶

Normally the header comments of each generated C/C++ source file includes a timestamp corresponding to when the file was generated. This option suppresses the inclusion of the timestamp.

--plugin <PLUGIN> , -t <PLUGIN> ¶

If Qt has been built as static libraries then the static plugin <PLUGIN> will be linked with the appropriate PyQt4 module. The option may be specified any number of times.

--protected-is-public ¶

On certain platforms the size of PyQt4 modules can be significantly reduced by redefining the C++ protected keyword as public during compilation. This option enables this behaviour and is the default on Linux and MacOS/X.

--protected-not-public ¶

The default redefinition of protected to public during compilation on Linux and MacOS/X is disabled.

--pyuic4-interpreter <FILE> ¶

<FILE> is the name of the Python interpreter used in the pyuic4 wrapper. The default is platform dependent.

--qmake <FILE> , -q <FILE> ¶

Qt 的 qmake program is used to determine how your Qt installation is laid out. Normally qmake is found on your PATH . This option can be used to specify a particular instance of qmake to use. This option is not available on Windows where qmake must be on PATH .

--qsci-api , -a ¶

PyQt4.api QScintilla API file is installed even if QScintilla does not appear to be installed. This option is implied if the --qsci-api-destdir option is specified.

--qsci-api-destdir <DIR> , -n <DIR> ¶

The QScintilla API file will be installed in the python subdirectory of the api subdirectory of the directory <DIR> .

--sip <FILE> ¶

sip program is used to generate PyQt4's C++ source code. Normally sip is found on your PATH . This option can be used to specify a particular instance of sip to use.

--sip-incdir <DIR> ¶

sip.h header file can be found in the directory <DIR> .

--sipdir <DIR> , -v <DIR> ¶

.sip files for the PyQt4 modules will be installed in the directory <DIR> .

--spec <SPEC> ¶

The argument -spec SPEC will be passed to qmake . The default behaviour is platform specific. On Windows configure-ng.py will choose the value that is correct for the version of Python that is being used. (However if you have built Python yourself then you may need to explicitly specify <SPEC> .) On MacOS configure-ng.py will try and avoid macx-xcode if possible.)

--static , -k ¶

The PyQt4 modules will be built as static libraries. This is useful when building a custom interpreter with the PyQt4 modules built in to the interpreter.

--sysroot <DIR> ¶

New in version 4.11.

<DIR> is the name of an optional directory that replaces sys.prefix in the names of other directories (specifically those specifying where the various PyQt4 components will be installed and where the Python include and library directories can be found). It is typically used when cross-compiling or when building a static version of PyQt4. See 采用配置文件进行配置 .

--target-py-version <VERSION> ¶

New in version 4.11.

<VERSION> is the major and minor version (e.g. 3.4 ) of the version of Python being targetted. By default the version of Python being used to run the configure.py script is used. It is typically used when cross-compiling. See 采用配置文件进行配置 .

--trace , -r ¶

The generated PyQt4 modules contain additional tracing code that is enabled using SIP's sip.settracemask() 函数。

--verbose , -w ¶

Compiler commands and any output issued during configuration is displayed instead of being suppressed. Use this if configure-ng.py is having problems to see what exactly is going wrong.

--version ¶

Display the PyQt4 version number.

Any remaining command line arguments are expected to be in the form name=value or name+=value . Such arguments are added to any qmake .pro file created by configure-ng.py .

使用 configure.py ¶

configure.py script is used to configure PyQt4 as follows:

python configure.py
									

This assumes that the Python interpreter is on your path. Something like the following may be appropriate on Windows:

c:\python34\python configure.py
									

If you have multiple versions of Python installed then make sure you use the interpreter for which you wish to build PyQt4 for.

The full set of command line options is:

--assume-shared ¶

Normally Qt is checked to see if it has been built as shared libraries. Some Linux distributions configure their Qt builds to make this check unreliable. This option ignores the result of the check and assumes that Qt has been built as shared libraries.

--bindir <DIR> , -b <DIR> ¶

pyuic4 , pyrcc4 and pylupdate4 utilities will be installed in the directory <DIR> .

--concatenate , -c ¶

The C++ source files for a Python module will be concatenated. This results in significantly reduced compilation times. Most, but not all, C++ compilers can handle the large files that result. See also the --concatenate-split 选项。

--concatenate-split <N> , -j <N> ¶

若 --concatenate option is used to concatenate the C++ source files then this option determines how many files are created. The default is 1.

--confirm-license ¶

Using this confirms that you accept the terms of the PyQt4 license.

--consolidate , -g ¶

Normally each PyQt4 module (except for the Qt module) is linked against the corresponding Qt library. This option creates a module called _qt which is linked against all the required Qt libraries and the other modules are stub modules that populate their module dictionaries from this one. This is useful when linking against static Qt libraries to eliminate the need to distribute the Qt libraries while minimising the memory footprint of the PyQt4 modules.

--dbus <DIR> , -s <DIR> ¶

dbus-python.h header file of the dbus-python package can be found in the directory <DIR>/dbus .

--debug , -u ¶

The PyQt4 modules will be built with debugging symbols. On Windows this requires that a debug version of Python is installed.

--destdir <DIR> , -d <DIR> ¶

The PyQt4 Python package will be installed in the directory <DIR> . The default is the Python installation's site-packages directory. If you use this option then the PYTHONPATH environment variable must include <DIR> .

--enable <MODULE> , -e <MODULE> ¶

Normally all PyQt4 modules are enabled and are built if the corresponding Qt library can be found. Using this option only those modules specifically enabled will be checked for and built. The option may be specified any number of times.

--help , -h ¶

Display a help message.

--no-deprecated ¶

All Qt v4 features that have been deprecated in Qt v5 will be disabled. This is useful when porting PyQt4 applications to PyQt5.

--no-designer-plugin ¶

The Qt Designer plugin will not be built.

--no-docstrings ¶

The PyQt4 modules will not contain automatically generated docstrings.

--no-qsci-api ¶

PyQt4.api QScintilla API file is not installed even if QScintilla does appear to be installed.

--no-sip-files ¶

.sip files for the PyQt4 modules will not be installed.

--no-timestamp , -T ¶

Normally the header comments of each generated C/C++ source file includes a timestamp corresponding to when the file was generated. This option suppresses the inclusion of the timestamp.

--plugin <PLUGIN> , -t <PLUGIN> ¶

If Qt has been built as static libraries then the static plugin <PLUGIN> will be linked with the appropriate PyQt4 module. The option may be specified any number of times.

--plugin-destdir <DIR> , -p <DIR> ¶

The Qt Designer plugin that manages plugins implemented in Python will be installed in the designer subdirectory of the directory <DIR> .

--protected-is-public ¶

On certain platforms the size of PyQt4 modules can be significantly reduced by redefining the C++ protected keyword as public during compilation. This option enables this behaviour and is the default on Linux and MacOS/X.

--protected-not-public ¶

The default redefinition of protected to public during compilation on Linux and MacOS/X is disabled.

--qmake <FILE> , -q <FILE> ¶

Qt 的 qmake program is used to determine how your Qt installation is laid out. Normally qmake is found on your PATH . This option can be used to specify a particular instance of qmake to use. This option is not available on Windows.

--qsci-api , -a ¶

PyQt4.api QScintilla API file is installed even if QScintilla does not appear to be installed. This option is implied if the --qsci-api-destdir option is specified.

--qsci-api-destdir <DIR> , -n <DIR> ¶

The QScintilla API file will be installed in the python subdirectory of the api subdirectory of the directory <DIR> .

--sipdir <DIR> , -v <DIR> ¶

.sip files for the PyQt4 modules will be installed in the directory <DIR> .

--static , -k ¶

The PyQt4 modules will be built as static libraries. This is useful when building a custom interpreter with the PyQt4 modules built in to the interpreter.

--trace , -r ¶

The generated PyQt4 modules contain additional tracing code that is enabled using SIP's sip.settracemask() 函数。

--use-arch <ARCH> ¶

When pyuic4 calls the Python interpreter on MacOS it will be run using the architecture <ARCH> . See the section Configuring SIP and PyQt4 for MacOS .

--verbose , -w ¶

Compiler commands and any output issued during configuration is displayed instead of being suppressed. Use this if configure.py is having problems to see what exactly is going wrong.

--version ¶

Display the PyQt4 version number.

Configuring SIP and PyQt4 for MacOS ¶

Note that this section only applies if you are using the configure.py script to configure PyQt4. The configure-ng.py script leaves it to Qt's qmake program to handle the details. configure-ng.py does not support the creation of universal binaries.

Building applications for MacOS can be a complex process. Typically the following need to be taken into account:

• the architectures (i.e. i386, x86_64, ppc) that you want to support
• the earliest version of MacOS you want to support (i.e. the deployment target)
• the version of the SDK you want to use.

If you are using a binary installer for Python and/or Qt then you also need to consider how they have been built regarding the above, and what bugs they have.

SIP's and PyQt4's configure.py scripts provide the necessary command line options to allow the correct configurations to be specified - the trick is to work out which options to use depending on the versions of Python and Qt you have installed.

SIP provides the following command line options to its configure.py 脚本。

• --arch <ARCH> specifies the target architecture and may be specified a number of times.
• --universal is a shortcut for --arch i386 --arch ppc .
• --deployment-target <VERSION> specifies the earliest version of MacOS you want to support. This sets the MACOSX_DEPLOYMENT_TARGET environment variable and should be used rather than setting the environment variable in the shell (to work around bugs in some versions of Python).
• --sdk <SDK> specifies the SDK to use.

PyQt4 provides the --use-arch option that specifies which architecture certain PyQt4 tools (actually only pyuic4 at the moment) will use when running Python. For example, if your Qt installation is 32 bits, and your Python installation is 32 bits and 64 bits then you will need to specify --use-arch i386 to ensure that pyuic4 runs the 32 bit version of Python.