Leander Beernaert 69fb4ae343 Distinguish between qt_plugin and regular plugins ... If we do not encounter the load(qt_plugin) statement in the .pro file but we do see the entry CONFIG+=plugin, treat the target as a regular CMake library instead of treating it as a qt_plugin by default. Change-Id: I67ad5c865a1a5ab691a6b0d86c2db4b686aa04dd Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>		2019-10-28 09:20:37 +00:00
..
debugplugin	Distinguish between qt_plugin and regular plugins	2019-10-28 09:20:37 +00:00
invalidplugin	Distinguish between qt_plugin and regular plugins	2019-10-28 09:20:37 +00:00
releaseplugin	Distinguish between qt_plugin and regular plugins	2019-10-28 09:20:37 +00:00
.gitignore	Moving relevant tests to corelib/plugin	2011-09-01 12:42:51 +02:00
.prev_CMakeLists.txt	Convert corelib plugin tests	2019-10-21 11:17:20 +00:00
CMakeLists.txt	Convert corelib plugin tests	2019-10-21 11:17:20 +00:00
qplugin.pro	Plugins: fix crash if the binary JSON data contains invalid size	2018-07-19 07:27:02 +00:00
tst_qplugin.cpp	Skip tests if the required plugins were not deployed	2019-06-19 17:03:53 +02:00
tst_qplugin.pro	Plugins: store the metadata in CBOR instead of binary JSON	2018-09-01 15:19:39 +00:00