Changeset 561 for trunk/doc/src/deployment
- Timestamp:
- Feb 11, 2010, 11:19:06 PM (15 years ago)
- Location:
- trunk
- Files:
-
- 1 edited
- 5 copied
Legend:
- Unmodified
- Added
- Removed
-
trunk
-
Property svn:mergeinfo
set to (toggle deleted branches)
/branches/vendor/nokia/qt/4.6.1 merged eligible /branches/vendor/nokia/qt/current merged eligible /branches/vendor/trolltech/qt/current 3-149
-
Property svn:mergeinfo
set to (toggle deleted branches)
-
trunk/doc/src/deployment/qt-conf.qdoc
r560 r561 57 57 libraries look elsewhere. 58 58 59 Note that on OS/2, the libraries do not use the hard-coded paths 60 by default. Instead, they look for plugins and other components in a 61 directory that contains the QtCore DLL library (or the application 62 executable if Qt is built as a static library). This behavior may 63 also be overridden using the \c qt.conf file. 64 59 65 QLibraryInfo will load \c qt.conf from one of the following locations: 60 66 … … 71 77 \endlist 72 78 79 On OS/2, if neither of the above locations contains \c qt.conf, 80 QLibraryInfo will additionally try the following two locations: 81 82 \list 1 83 84 \o \c qt.conf in the directory containing the QtCore DLL library 85 (or the application executable if Qt is built as a static library) 86 87 \o \c %ETC%\qtsys.conf 88 89 \endlist 90 73 91 The \c qt.conf file is an INI text file, as described in the \l 74 92 {QSettings::Format}{QSettings} documentation. The file should have … … 105 123 need to be placed in specific sub-directories under the 106 124 \c{plugins} directory (see \l{How to Create Qt Plugins} for 107 details). 108 125 details). On OS/2, the \c Prefix is always relative to the directory 126 where \c qt.conf or \c qtsys.conf is loaded from. 127 109 128 For example, a \c qt.conf file could contain the following: 110 129
Note:
See TracChangeset
for help on using the changeset viewer.