Ignore:
Timestamp:
Feb 11, 2010, 11:19:06 PM (15 years ago)
Author:
Dmitry A. Kuminov
Message:

trunk: Merged in qt 4.6.1 sources.

Location:
trunk
Files:
1 edited
2 copied

Legend:

Unmodified
Added
Removed
  • trunk

  • trunk/doc/src/deployment/qt-conf.qdoc

    r560 r561  
    5757    libraries look elsewhere.
    5858
     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   
    5965    QLibraryInfo will load \c qt.conf from one of the following locations:
    6066
     
    7177    \endlist
    7278
     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   
    7391    The \c qt.conf file is an INI text file, as described in the \l
    7492    {QSettings::Format}{QSettings} documentation. The file should have
     
    105123    need to be placed in specific sub-directories under the
    106124    \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   
    109128    For example, a \c qt.conf file could contain the following:
    110129
Note: See TracChangeset for help on using the changeset viewer.