diff options
| -rw-r--r-- | doc/src/deployment/deployment.qdoc | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/doc/src/deployment/deployment.qdoc b/doc/src/deployment/deployment.qdoc index 6a1760e..1459e6a 100644 --- a/doc/src/deployment/deployment.qdoc +++ b/doc/src/deployment/deployment.qdoc @@ -110,6 +110,7 @@ \o \l {QtXmlPatterns} \o \l {Phonon Module}{Phonon} \o \l {Qt3Support} + \o \endtable Since Qt is not a system library, it has to be redistributed along @@ -117,10 +118,15 @@ of the libraries used by the application. Using static linking, however, the Qt run-time is compiled into the executable. - In particular, you will need to deploy Qt plugins, such as - JPEG support or SQL drivers. For more information about plugins, - see the \l {plugins-howto.html}{How to Create Qt Plugins} - documentation. + In general, you should deploy all plugins that your build of Qt uses, + excluding only those that you have identified as being unnecessary + for your application and its users. + + For instance, you may need to deploy plugins for JPEG support and + SQL drivers, but you should also deploy plugins that your users may + require, including those for accessibility. + For more information about plugins, see the + \l{plugins-howto.html}{How to Create Qt Plugins} documentation. When deploying an application using the shared library approach you must ensure that the Qt libraries will use the correct path to |