On 12/5/18 5:01 PM, Alan W. Irwin wrote:
> But I still don't understand exactly how ctest is run from cmake. Assuming
> the
> "test" target (which I have never tried) runs the "all" target and then ctest,
> I guess
>
> cmake --build . --config Debug --target test
>
> would run ctest indirectly
On 2018-12-05 12:37-0800 Alan W. Irwin wrote:
On 2018-12-05 09:22-0500 Brad King via cmake-developers wrote:
On 12/4/18 4:08 PM, Alan W. Irwin wrote:
Build Warnings (1)
*** WARNING non-zero return value in ctest from:
C:\cmake-3.13.1-win64-x64\bin\cmake.exe
That's in the "Build"
On 2018-12-05 09:22-0500 Brad King via cmake-developers wrote:
On 12/4/18 4:08 PM, Alan W. Irwin wrote:
Build Warnings (1)
*** WARNING non-zero return value in ctest from:
C:\cmake-3.13.1-win64-x64\bin\cmake.exe
That's in the "Build" section and indicates that the build command
exited
On 12/4/18 4:08 PM, Alan W. Irwin wrote:
> Build Warnings (1)
>
> *** WARNING non-zero return value in ctest from:
> C:\cmake-3.13.1-win64-x64\bin\cmake.exe
That's in the "Build" section and indicates that the build command
exited with non-zero status. If you want to try to reproduce that
by
