source: trunk/doc/src/deployment/qt-conf.qdoc@ 846

Last change on this file since 846 was 846, checked in by Dmitry A. Kuminov, 14 years ago

trunk: Merged in qt 4.7.2 sources from branches/vendor/nokia/qt.

  • Property svn:eol-style set to native
File size: 5.6 KB
Line 
1/****************************************************************************
2**
3** Copyright (C) 2011 Nokia Corporation and/or its subsidiary(-ies).
4** All rights reserved.
5** Contact: Nokia Corporation ([email protected])
6**
7** This file is part of the documentation of the Qt Toolkit.
8**
9** $QT_BEGIN_LICENSE:FDL$
10** Commercial Usage
11** Licensees holding valid Qt Commercial licenses may use this file in
12** accordance with the Qt Commercial License Agreement provided with the
13** Software or, alternatively, in accordance with the terms contained in a
14** written agreement between you and Nokia.
15**
16** GNU Free Documentation License
17** Alternatively, this file may be used under the terms of the GNU Free
18** Documentation License version 1.3 as published by the Free Software
19** Foundation and appearing in the file included in the packaging of this
20** file.
21**
22** If you have questions regarding the use of this file, please contact
23** Nokia at [email protected].
24** $QT_END_LICENSE$
25**
26****************************************************************************/
27
28/*!
29 \page qt-conf.html
30
31 \title Using qt.conf
32
33 The \c qt.conf file overrides the hard-coded paths that are
34 compiled into the Qt library. These paths are accessible using the
35 QLibraryInfo class. Without \c qt.conf, the functions in
36 QLibraryInfo return these hard-coded paths; otherwise they return
37 the paths as specified in \c qt.conf.
38
39 Without \c qt.conf, the Qt libraries will use the hard-coded paths
40 to look for plugins, translations, and so on. These paths may not
41 exist on the target system, or they may not be
42 accesssible. Because of this, you need \c qt.conf to make the Qt
43 libraries look elsewhere.
44
45 Note that on OS/2, the libraries do not use the hard-coded paths
46 by default. Instead, they look for plugins and other components in a
47 directory that contains the QtCore DLL library (or the application
48 executable if Qt is built as a static library). This behavior may
49 also be overridden using the \c qt.conf file.
50
51 QLibraryInfo will load \c qt.conf from one of the following locations:
52
53 \list 1
54
55 \o \c :/qt/etc/qt.conf using the resource system
56
57 \o on Mac OS X, in the Resource directory inside the appliction
58 bundle, for example \c assistant.app/Contents/Resources/qt.conf
59
60 \o in the directory containing the application executable, i.e.
61 QCoreApplication::applicationDirPath() + QDir::separator() + "qt.conf"
62
63 \endlist
64
65 On OS/2, if neither of the above locations contains \c qt.conf,