[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-buildsystem
Subject:    EXECUTABLE_OUTPUT_PATH for tests
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2007-09-19 22:40:16
Message-ID: 200709191840.16184.neundorf () kde ! org
[Download RAW message or body]

Hi,

currently KDE4_ADD_TEST_EXECUTABLE and KDE4_ADD_UNIT_TEST set 
EXECUTABLE_OUTPUT_PATH back from bin/ to the current directory.

I think this is a bad idea in general.

Imagine this cmake code:

add_executable(foo main.cpp)
add_executable(bar bar.c)

 
As it is now both foo and bar will end up in bin/.
Now somebody adds a test executable:

add_executable(foo main.cpp)
kde4_add_test_executable(test1 test.cpp)
add_executable(bar bar.c)


Now foo and bar will no longer be created in bin/, but in the current 
directory.
It is very unobvious why this happens.

If there are no really good reasons for this behaviour I am very much in 
favour of removing the modification of EXECUTABLE_OUTPUT_PATH in the 
KDE4_ADD_TEST_EXECUTABLE (which will be part of KDE4_ADD_EXECUTABLE next 
week) and also from KDE4_ADD_UNIT_TEST.

Alex
_______________________________________________
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
[prev in list] [next in list] [prev in thread] [next in thread]