1 | /****************************************************************************
|
---|
2 | **
|
---|
3 | ** Copyright (C) 2009 Nokia Corporation and/or its subsidiary(-ies).
|
---|
4 | ** Contact: Qt Software Information ([email protected])
|
---|
5 | **
|
---|
6 | ** This file is part of the QtCore module of the Qt Toolkit.
|
---|
7 | **
|
---|
8 | ** $QT_BEGIN_LICENSE:LGPL$
|
---|
9 | ** Commercial Usage
|
---|
10 | ** Licensees holding valid Qt Commercial licenses may use this file in
|
---|
11 | ** accordance with the Qt Commercial License Agreement provided with the
|
---|
12 | ** Software or, alternatively, in accordance with the terms contained in
|
---|
13 | ** a written agreement between you and Nokia.
|
---|
14 | **
|
---|
15 | ** GNU Lesser General Public License Usage
|
---|
16 | ** Alternatively, this file may be used under the terms of the GNU Lesser
|
---|
17 | ** General Public License version 2.1 as published by the Free Software
|
---|
18 | ** Foundation and appearing in the file LICENSE.LGPL included in the
|
---|
19 | ** packaging of this file. Please review the following information to
|
---|
20 | ** ensure the GNU Lesser General Public License version 2.1 requirements
|
---|
21 | ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
|
---|
22 | **
|
---|
23 | ** In addition, as a special exception, Nokia gives you certain
|
---|
24 | ** additional rights. These rights are described in the Nokia Qt LGPL
|
---|
25 | ** Exception version 1.0, included in the file LGPL_EXCEPTION.txt in this
|
---|
26 | ** package.
|
---|
27 | **
|
---|
28 | ** GNU General Public License Usage
|
---|
29 | ** Alternatively, this file may be used under the terms of the GNU
|
---|
30 | ** General Public License version 3.0 as published by the Free Software
|
---|
31 | ** Foundation and appearing in the file LICENSE.GPL included in the
|
---|
32 | ** packaging of this file. Please review the following information to
|
---|
33 | ** ensure the GNU General Public License version 3.0 requirements will be
|
---|
34 | ** met: http://www.gnu.org/copyleft/gpl.html.
|
---|
35 | **
|
---|
36 | ** If you are unsure which license is appropriate for your use, please
|
---|
37 | ** contact the sales department at [email protected].
|
---|
38 | ** $QT_END_LICENSE$
|
---|
39 | **
|
---|
40 | ****************************************************************************/
|
---|
41 |
|
---|
42 | #include "qplatformdefs.h"
|
---|
43 |
|
---|
44 | #include "qplugin.h"
|
---|
45 | #include "qpluginloader.h"
|
---|
46 | #include <qfileinfo.h>
|
---|
47 | #include "qlibrary_p.h"
|
---|
48 | #include "qdebug.h"
|
---|
49 |
|
---|
50 | #ifndef QT_NO_LIBRARY
|
---|
51 |
|
---|
52 | QT_BEGIN_NAMESPACE
|
---|
53 |
|
---|
54 | /*!
|
---|
55 | \class QPluginLoader
|
---|
56 | \reentrant
|
---|
57 | \brief The QPluginLoader class loads a plugin at run-time.
|
---|
58 |
|
---|
59 | \mainclass
|
---|
60 | \ingroup plugins
|
---|
61 |
|
---|
62 | QPluginLoader provides access to a \l{How to Create Qt
|
---|
63 | Plugins}{Qt plugin}. A Qt plugin is stored in a shared library (a
|
---|
64 | DLL) and offers these benefits over shared libraries accessed
|
---|
65 | using QLibrary:
|
---|
66 |
|
---|
67 | \list
|
---|
68 | \o QPluginLoader checks that a plugin is linked against the same
|
---|
69 | version of Qt as the application.
|
---|
70 | \o QPluginLoader provides direct access to a root component object
|
---|
71 | (instance()), instead of forcing you to resolve a C function manually.
|
---|
72 | \endlist
|
---|
73 |
|
---|
74 | An instance of a QPluginLoader object operates on a single shared
|
---|
75 | library file, which we call a plugin. It provides access to the
|
---|
76 | functionality in the plugin in a platform-independent way. To
|
---|
77 | specify which plugin to load, either pass a file name in
|
---|
78 | the constructor or set it with setFileName().
|
---|
79 |
|
---|
80 | The most important functions are load() to dynamically load the
|
---|
81 | plugin file, isLoaded() to check whether loading was successful,
|
---|
82 | and instance() to access the root component in the plugin. The
|
---|
83 | instance() function implicitly tries to load the plugin if it has
|
---|
84 | not been loaded yet. Multiple instances of QPluginLoader can be
|
---|
85 | used to access the same physical plugin.
|
---|
86 |
|
---|
87 | Once loaded, plugins remain in memory until all instances of
|
---|
88 | QPluginLoader has been unloaded, or until the application
|
---|
89 | terminates. You can attempt to unload a plugin using unload(),
|
---|
90 | but if other instances of QPluginLoader are using the same
|
---|
91 | library, the call will fail, and unloading will only happen when
|
---|
92 | every instance has called unload(). Right before the unloading
|
---|
93 | happen, the root component will also be deleted.
|
---|
94 |
|
---|
95 | In order to speed up loading and validation of plugins, some of
|
---|
96 | the information that is collected during loading is cached in
|
---|
97 | persistent memory (through QSettings). For instance, the result
|
---|
98 | of a load operation (e.g. succeeded or failed) is stored in the
|
---|
99 | cache, so that subsequent load operations don't try to load an
|
---|
100 | invalid plugin. However, if the "last modified" timestamp of
|
---|
101 | a plugin has changed, the plugin's cache entry is invalidated
|
---|
102 | and the plugin is reloaded regardless of the values in the cache
|
---|
103 | entry. The cache entry is then updated with the new result of the
|
---|
104 | load operation.
|
---|
105 |
|
---|
106 | This also means that the timestamp must be updated each time the
|
---|
107 | plugin or any dependent resources (such as a shared library) is
|
---|
108 | updated, since the dependent resources might influence the result
|
---|
109 | of loading a plugin.
|
---|
110 |
|
---|
111 | See \l{How to Create Qt Plugins} for more information about
|
---|
112 | how to make your application extensible through plugins.
|
---|
113 |
|
---|
114 | Note that the QPluginLoader cannot be used if your application is
|
---|
115 | statically linked against Qt. In this case, you will also have to
|
---|
116 | link to plugins statically. You can use QLibrary if you need to
|
---|
117 | load dynamic libraries in a statically linked application.
|
---|
118 |
|
---|
119 | \sa QLibrary, {Plug & Paint Example}
|
---|
120 | */
|
---|
121 |
|
---|
122 | /*!
|
---|
123 | Constructs a plugin loader with the given \a parent.
|
---|
124 | */
|
---|
125 | QPluginLoader::QPluginLoader(QObject *parent)
|
---|
126 | : QObject(parent), d(0), did_load(false)
|
---|
127 | {
|
---|
128 | }
|
---|
129 |
|
---|
130 | /*!
|
---|
131 | Constructs a plugin loader with the given \a parent that will
|
---|
132 | load the plugin specified by \a fileName.
|
---|
|
---|