Name Description Size Coverage
qcoffpeparser.cpp 15285 -
qcoffpeparser_p.h 811 -
qelfparser_p.cpp 27264 -
qelfparser_p.h 760 -
qfactoryinterface.cpp 307 -
qfactoryinterface.h 601 -
qfactoryloader.cpp 21017 -
qfactoryloader_p.h 3563 -
qlibrary.cpp 40160 -
qlibrary.h 2277 -
qlibrary_p.h 3595 -
qlibrary_unix.cpp 9480 -
qlibrary_win.cpp 3709 -
qmachparser.cpp 10307 -
qmachparser_p.h 842 -
qplugin.h 10901 -
qplugin.qdoc 2528 -
qplugin_p.h not output by moc in CBOR 4667 -
qpluginloader.cpp ! \class QPluginLoader \inmodule QtCore \reentrant \brief The QPluginLoader class loads a plugin at run-time. \ingroup plugins QPluginLoader provides access to a \l{How to Create Qt Plugins}{Qt plugin}. A Qt plugin is stored in a shared library (a DLL) and offers these benefits over shared libraries accessed using QLibrary: \list \li QPluginLoader checks that a plugin is linked against the same version of Qt as the application. \li QPluginLoader provides direct access to a root component object (instance()), instead of forcing you to resolve a C function manually. \endlist An instance of a QPluginLoader object operates on a single shared library file, which we call a plugin. It provides access to the functionality in the plugin in a platform-independent way. To specify which plugin to load, either pass a file name in the constructor or set it with setFileName(). The most important functions are load() to dynamically load the plugin file, isLoaded() to check whether loading was successful, and instance() to access the root component in the plugin. The instance() function implicitly tries to load the plugin if it has not been loaded yet. Multiple instances of QPluginLoader can be used to access the same physical plugin. Once loaded, plugins remain in memory until all instances of QPluginLoader has been unloaded, or until the application terminates. You can attempt to unload a plugin using unload(), but if other instances of QPluginLoader are using the same library, the call will fail, and unloading will only happen when every instance has called unload(). Right before the unloading happens, the root component will also be deleted. See \l{How to Create Qt Plugins} for more information about how to make your application extensible through plugins. Note that the QPluginLoader cannot be used if your application is statically linked against Qt. In this case, you will also have to link to plugins statically. You can use QLibrary if you need to load dynamic libraries in a statically linked application. \sa QLibrary 14906 -
qpluginloader.h 1558 -
qsystemlibrary.cpp ! \internal \class QSystemLibrary \inmodule QtCore The purpose of this class is to load only libraries that are located in well-known and trusted locations on the filesystem. It does not suffer from the security problem that QLibrary has, therefore it will never search in the current directory. The search order is the same as the order in DLL Safe search mode Windows, except that we don't search: The current directory The 16-bit system directory. (normally \c{c:\windows\system}) The Windows directory. (normally \c{c:\windows}) This means that the effective search order is: 1. Application path. 2. System libraries path. 3. Trying all paths inside the PATH environment variable. Note, when onlySystemDirectory is true it will skip 1) and 3). DLL Safe search mode is documented in the "Dynamic-Link Library Search Order" document on MSDN. 2981 -
qsystemlibrary_p.h 1831 -
quuid.cpp ! \internal Parses the string representation of a UUID (with optional surrounding "{}") by reading at most MaxStringUuidLength (38) characters from \a src, which may be \nullptr. Stops at the first invalid character (which includes a premature NUL). Returns the successfully parsed QUuid, or a null QUuid in case of failure. 28240 -
quuid.h 14995 -
quuid_p.h 1954 -