From d8307c727034000681ae442ae07c3d232a1653d3 Mon Sep 17 00:00:00 2001 From: Kevin Funk Date: Thu, 10 Aug 2017 01:20:30 +0200 Subject: Revert "RFC: Make ECMAddTests respect BUILD_TESTING" This broke a lot of frameworks when built WITH BUILD_TESTING=OFF. I didn't notice before since kdesrc-build was appending BUILD_TESTING=TRUE thus re-enabling the tests for me... This reverts commit b99d2d2c5dedcaba9745dddc1dd7b8d4811babf1. --- modules/ECMAddTests.cmake | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/modules/ECMAddTests.cmake b/modules/ECMAddTests.cmake index c77a7aaf..96673888 100644 --- a/modules/ECMAddTests.cmake +++ b/modules/ECMAddTests.cmake @@ -49,12 +49,6 @@ # be given; this will be used for both the target and test names (and, as with # ecm_add_tests(), the NAME_PREFIX argument will be prepended to the test name). # -# If BUILD_TESTING is set to OFF, ecm_add_test will turn into a no-op and thus -# will not add any test-related targets -# -# BUILD_TESTING is created as a cache variable by the CTest module and by the -# :kde-module:`KDECMakeSettings` module. -# # # Since pre-1.0.0. @@ -90,10 +84,6 @@ include(ECMMarkAsTest) include(ECMMarkNonGuiExecutable) function(ecm_add_test) - if(NOT BUILD_TESTING) - return() # turn this function into a no-op - endif() - set(options GUI) # TARGET_NAME_VAR and TEST_NAME_VAR are undocumented args used by # ecm_add_tests -- cgit v1.2.1