[Cdash] Problem with cdash, subprojects and CTEST_USE_LAUNCHERS=TRUE ?

[Alexander Neundorf]

On Friday 17 August 2012, Alexander Neundorf wrote:
> On Friday 17 August 2012, David Cole wrote:
> > On Fri, Aug 17, 2012 at 2:17 PM, Alexander Neundorf 
<neundorf at kde.org>wrote:
> > > **
> > > 
> > > On Friday 17 August 2012, David Cole wrote:
> > > 
> > > ...
> > > 
> > > > the -S script. Next, start adding printf debugging if necessary to
> > > > the
> > > 
> > > code
> > > 
> > > > where the return values of launcher-launched programs are being
> > > 
> > > calculated.
> > > 
> > > I guess cmCTestLaunch::IsError() etc ?
> > > 
> > > Alex
> > 
> > Unfortunately, it's been a long time since I looked at that particular
> > ctest code in such depth. I'd have to investigate just as much as you to
> > figure it out.
> 
> Ok. I'm looking into it.
> This is what I get:
> 
> ....
> gmake[2]: *** [Foo/Bar] Error 1
> gmake[1]: *** [Foo/CMakeFiles/Bar.dir/all] Error 2
> gmake: *** [all] Error 2
>  Size of output: 112K
> Command exited with the value: 2
> MakeCommand:/usr/bin/gmake
> Error(s) when building project
>    0 Compiler errors
>    1 Compiler warnings
> SetCTestConfiguration:DropMethod:http
> ...
> 
> I guess I'll find something...

Found it.
The projects where it didn't work didn't have
include(CTest)
in their CMakeLists.txt
Including this file made it work.
I haven't figured out which exact setting is causing this, but I think it 
would be good if ctest would error with if CTEST_USE_LAUNCHERS is TRUE but 
CTest.cmake has not been included (or the appropriate variable been set).
I guess it's the CTEST_LAUNCH_COMPILE/LINK/CUSTOM variables/global 
properties...

Alex