qt5base-lts/tests/auto/cmake
Stephen Kelly f16a77d783 Use IF(NOT TARGET ...) before creating imported targets.
Initially we didn't do this because someone could accidentally create
another target of a conflicting name, and used a variable to store whether we
have created the target already or not.

That wasn't adequeate to deal with finding the package in a scope
like a function, so we used a directory property. However, the directory
property is not valid in the same scopes as the defined target. For
example, finding a Qt module in both a directory and a subdirectory causes
a conflict.

As it is already unlikely that a target would be accidentally created with
a name like Qt5::Core, we should simply use the IF(TARGET) form.

Change-Id: If64f25d45f51edcd1edb0d4bfb5ed3bb2479bd27
Reviewed-by: David Faure <faure@kde.org>
2012-05-15 23:03:23 +02:00
..
fail4 Move the CMake unit tests to auto/ 2012-04-23 17:03:56 +02:00
fail5 Move the CMake unit tests to auto/ 2012-04-23 17:03:56 +02:00
pass1 Find Qt5 modules automatically in the qt5_use_modules function. 2012-05-14 04:35:01 +02:00
pass2 Move the CMake unit tests to auto/ 2012-04-23 17:03:56 +02:00
pass3 Move the CMake unit tests to auto/ 2012-04-23 17:03:56 +02:00
pass7 Move the CMake unit tests to auto/ 2012-04-23 17:03:56 +02:00
pass8 Move the CMake unit tests to auto/ 2012-04-23 17:03:56 +02:00
pass9 Move the CMake unit tests to auto/ 2012-04-23 17:03:56 +02:00
pass10 Use IF(NOT TARGET ...) before creating imported targets. 2012-05-15 23:03:23 +02:00
pass(needsquoting)6 Revert "Don't use the pri depends line for link dependencies." 2012-05-03 16:11:58 +02:00
cmake.pro Never attempt to run the dbus tests on APPLE. 2012-05-01 07:10:23 +02:00
CMakeLists.txt Use IF(NOT TARGET ...) before creating imported targets. 2012-05-15 23:03:23 +02:00