Changeset 357 for trunk/doc/src/qt-conf.qdoc

Timestamp:

Nov 28, 2009, 8:49:40 PM (16 years ago)

Author:

Dmitry A. Kuminov

Message:

corelib: Make the Qt library portable on OS/2 by replacing hard-coded paths with paths relative to the QtCore DLL (or the application executable if Qt is built as a static library). Add two new locations to search for qt.conf/qtsys.conf for providing more portability and easier system integration. See #78 for more details.

File:

• trunk/doc/src/qt-conf.qdoc (modified) (3 diffs)

trunk/doc/src/qt-conf.qdoc

@@ -58 +58 @@
     libraries look elsewhere.
 
+        Note that on OS/2, the libraries do not use the hard-coded paths
+        by default. Instead, they look for plugins and other components in a
+        directory that contains the QtCore DLL library (or the application
+        executable if Qt is built as a static library). This behavior may
+        also be overridden using the \c qt.conf file.
+    
     QLibraryInfo will load \c qt.conf from one of the following locations:
 
@@ -72 +78 @@
     \endlist
 
+    On OS/2, if neither of the above locations contains \c qt.conf,
+    QLibraryInfo will additionally try the following two locations:
+
+    \list 1
+
+    \o \c qt.conf in the directory containing the QtCore DLL library
+    (or the application executable if Qt is built as a static library)
+
+    \o \c %ETC%\qt\qtsys.conf
+    
+    \endlist
+    
     The \c qt.conf file is an INI text file, as described in the \l
     {QSettings::Format}{QSettings} documentation. The file should have
@@ -106 +124 @@
     need to be placed in specific sub-directories under the
     \c{plugins} directory (see \l{How to Create Qt Plugins} for
-    details).
-
+    details). On OS/2, the \c Prefix is always relative to the directory
+    where \c qt.conf or \c qtsys.conf is loaded from.
+    
     For example, a \c qt.conf file could contain the following: