mirror of
https://bitbucket.org/smil3y/katie.git
synced 2025-02-27 20:32:57 +00:00
121 lines
4 KiB
Text
121 lines
4 KiB
Text
/****************************************************************************
|
|
**
|
|
** Copyright (C) 2015 The Qt Company Ltd.
|
|
** Copyright (C) 2016-2019 Ivailo Monev
|
|
**
|
|
** This file is part of the documentation of the Qt Toolkit.
|
|
**
|
|
** $QT_BEGIN_LICENSE:FDL$
|
|
** Commercial License Usage
|
|
** Licensees holding valid commercial Qt licenses may use this file in
|
|
** accordance with the commercial license agreement provided with the
|
|
** Software or, alternatively, in accordance with the terms contained in
|
|
** a written agreement between you and The Qt Company. For licensing terms
|
|
** and conditions see http://www.qt.io/terms-conditions. For further
|
|
** information use the contact form at http://www.qt.io/contact-us.
|
|
**
|
|
** GNU Free Documentation License Usage
|
|
** Alternatively, this file may be used under the terms of the GNU Free
|
|
** Documentation License version 1.3 as published by the Free Software
|
|
** Foundation and appearing in the file included in the packaging of
|
|
** this file. Please review the following information to ensure
|
|
** the GNU Free Documentation License version 1.3 requirements
|
|
** will be met: http://www.gnu.org/copyleft/fdl.html.
|
|
** $QT_END_LICENSE$
|
|
**
|
|
****************************************************************************/
|
|
|
|
/*!
|
|
\headerfile <QtPlugin>
|
|
\title Macros for Defining Plugins
|
|
|
|
\brief The <QtPlugin> header files defines macros for defining plugins.
|
|
|
|
\sa {How to Create Qt Plugins}
|
|
*/
|
|
|
|
/*!
|
|
\macro Q_DECLARE_INTERFACE(ClassName, Identifier)
|
|
\relates <QtPlugin>
|
|
|
|
This macro associates the given \a Identifier (a string literal)
|
|
to the interface class called \a ClassName. The \a Identifier must
|
|
be unique. For example:
|
|
|
|
\snippet examples/tools/plugandpaint/interfaces.h 3
|
|
|
|
This macro is normally used right after the class definition for
|
|
\a ClassName, in a header file. See the
|
|
\l{tools/plugandpaint}{Plug & Paint} example for details.
|
|
|
|
If you want to use Q_DECLARE_INTERFACE with interface classes
|
|
declared in a namespace then you have to make sure the Q_DECLARE_INTERFACE
|
|
is not inside a namespace though. For example:
|
|
\snippet doc/src/snippets/code/doc_src_qplugin.cpp 0
|
|
|
|
\sa Q_INTERFACES(), Q_EXPORT_PLUGIN2(), {How to Create Qt Plugins}
|
|
*/
|
|
|
|
/*!
|
|
\macro Q_EXPORT_PLUGIN(ClassName)
|
|
\relates <QtPlugin>
|
|
\obsolete
|
|
|
|
Use Q_EXPORT_PLUGIN2() instead. This macro is equivalent to
|
|
Q_EXPORT_PLUGIN2(\a ClassName, \a ClassName).
|
|
*/
|
|
|
|
/*!
|
|
\macro Q_EXPORT_PLUGIN2(PluginName, ClassName)
|
|
\relates <QtPlugin>
|
|
\since 4.1
|
|
\keyword Q_EXPORT_PLUGIN2
|
|
|
|
This macro exports the plugin class \a ClassName for the plugin specified
|
|
by \a PluginName. The value of \a PluginName should correspond to the
|
|
\l{qmake Variable Reference#TARGET}{TARGET} specified in the plugin's
|
|
project file.
|
|
|
|
There should be exactly one occurrence of this macro in the source code
|
|
for a Qt plugin, and it should be used where the implementation is written
|
|
rather than in a header file.
|
|
|
|
Example:
|
|
|
|
\snippet doc/src/snippets/code/doc_src_qplugin.cpp 1
|
|
|
|
See the \l{tools/plugandpaint}{Plug & Paint} example for details.
|
|
|
|
\sa Q_DECLARE_INTERFACE(), {How to Create Qt Plugins}
|
|
*/
|
|
|
|
/*!
|
|
\macro Q_IMPORT_PLUGIN(PluginName)
|
|
\relates <QtPlugin>
|
|
|
|
This macro imports the plugin named \a PluginName, corresponding
|
|
to the \l{qmake Variable Reference#TARGET}{TARGET} specified in the
|
|
plugin's project file.
|
|
|
|
Inserting this macro into your application's source code will allow
|
|
you to make use of a static plugin.
|
|
|
|
Example:
|
|
|
|
\snippet doc/src/snippets/code/doc_src_qplugin.cpp 2
|
|
|
|
Static plugins must also be included by the linker when your
|
|
application is built. For Qt's predefined plugins,
|
|
you can use the \c QTPLUGIN to add
|
|
the required plugins to your build. For example:
|
|
|
|
\snippet doc/src/snippets/code/doc_src_qplugin.pro 3
|
|
|
|
\sa {Static Plugins}, {How to Create Qt Plugins}, {Using qmake}
|
|
*/
|
|
|
|
/*!
|
|
\macro Q_EXPORT_STATIC_PLUGIN(ClassName)
|
|
\relates <QtPlugin>
|
|
\internal
|
|
*/
|