| Tutorial | Classes | Functions | QSA Developer | Language | Library | Qt API | Qt Script for Applications | ![]() |
[Prev: Debugging Qt Script Applications] [Home]
This chapter explains how to deploy QSA-enabled applications, meaning which libraries and files have to be shipped with the application.
Qt Script for Applications requires and uses Qt. This means following libraries from your Qt installation have to be shipped with your application and installed in the user's library path, so that the operating system can locate these libraries:
<b>Unix filename</b>
<b>Windows filename</b>
<b>Description</b>
$QTDIR/lib/libqt.so
%QTDIR%{%VERSION%}.dll
The Qt library
$QTDIR/lib/libqui.so
Built static on windows,doesn't need to be shipped on windows.
Includes QWidgetFactory, which is required by QSA
Following libraries from your QSA installation have to be shipped with your application and installed in the user's library path, so that the operating system can locate these libraries:
<b>Unix filename</b>
<b>Windows filename</b>
<b>Description</b>
$QTDIR/lib/libqsa.so
%QTDIR%{%VERSION%}.dll
The QSA library (scripting engine, bindings, etc.)
Following plugins from your QSA installation have to be shipped with your application. They have to be installed in the Qt plugin path under the directory qsa. See QApplication::setLibraryPath() for details.
<b>Unix filename</b>
<b>Windows filename</b>
<b>Description</b>
$QTDIR/plugins/qsa/libquickide.so
%QTDIR%.dll
The QSA-specifc features for Qt Script for Applications Developer.
$QTDIR/plugins/qsa/libquickcustom.so
%QTDIR%.dll
Some custom classes (PaintWidget, etc.) provided by QSA
Copyright © 2001-2002 Trolltech | Trademarks | QSA version 1.0.0-beta1
|