Re: [CMake] CTest: Weird behaviour

2010-10-20 Thread Marcel Loose
On Tue, 2010-10-19 at 08:24 -0400, Bill Hoffman wrote: > On 10/19/2010 4:21 AM, Marcel Loose wrote: > > Hi all, > > > > I stumbled upon IMHO weird behaviour of CTest. > > It seems that compilation errors are not picked up, somehow. Look at the > > output of a run of "ctest -V -D ExperimentalBuild"

Re: [CMake] CTest: Weird behaviour

2010-10-19 Thread Bill Hoffman
On 10/19/2010 4:21 AM, Marcel Loose wrote: Hi all, I stumbled upon IMHO weird behaviour of CTest. It seems that compilation errors are not picked up, somehow. Look at the output of a run of "ctest -V -D ExperimentalBuild" below. /export/home/loose/work/LOFAR_trunk/LOFAR/LCS/pyparameterset/src/p

Re: [CMake] CTest: Weird behaviour

2010-10-19 Thread Michael Wild
On 19. Oct, 2010, at 10:21 , Marcel Loose wrote: > Hi all, > > I stumbled upon IMHO weird behaviour of CTest. > It seems that compilation errors are not picked up, somehow. Look at the > output of a run of "ctest -V -D ExperimentalBuild" below. > > /export/home/loose/work/LOFAR_trunk/LOFAR/LCS/

[CMake] CTest: Weird behaviour

2010-10-19 Thread Marcel Loose
Hi all, I stumbled upon IMHO weird behaviour of CTest. It seems that compilation errors are not picked up, somehow. Look at the output of a run of "ctest -V -D ExperimentalBuild" below. /export/home/loose/work/LOFAR_trunk/LOFAR/LCS/pyparameterset/src/pyparameterset.cc:22:27: error: lofar_config.h