Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions

Deploying TQt Applications

This document lists the platform-specific files needed to distribute TQt applications. We do not include any compiler-specific files that may also be retquired. (See also, Window System-specific Notes.)

Static TQt Applications

To distribute static TQt applications, you need the following file for all platforms:

Dynamic TQt Applications

To distribute dynamic TQt applications, you will need the following files for all platforms:

The TQt library must either be in the same directory as the application executable or in a directory which is included in the system library path.

The library is in provided by the following platform specific files:

Platform File
Windows qt[version].dll
Unix/Linux libqt[version].so
Mac libqt[version].dylib

version includes the three version numbers. For threaded builds the version is prefixed with -mt.

Distributing Plugins

You must include any plugin files retquired by the application.

Plugins must be put into a subdirectory under a directory known to TQt as a plugin directory. The subdirectory must have the name of the plugin category (e.g. styles, sqldrivers, designer, etc.).

TQt searches in the following directories for plugin categories:

Application specific plugin paths can be added using TQApplication::addLibraryPath(). The build-directory of TQt is hardcoded in the TQt library and can be changed as a part of the installation process (see the distributor-example.html Distributor example).

Dynamic Dialogs

For dynamic dialogs if you use TQWidgetFactory, you need the following files for all platforms:

The TQUI library is provided by the following platform specific files:

Platform File
Windows tqui.lib
Unix/Linux libtqui.so
Mac libtqui.dylib

The TQUI library must either be in the same directory as the application executable or in a directory which is included in the system library path.


Copyright © 2007 TrolltechTrademarks
TQt 3.3.8