Re: [CMake] Does a ctested build work with make -j

2014-01-28 Thread Bill Hoffman
On 1/27/2014 6:05 PM, Matthew Woehlke wrote: What would be the difference in this context between MAKECOMMAND and CMAKE_MAKE_PROGRAM? I was just reading somewhere¹ that prefers the latter... (¹ https://github.com/Slicer/Slicer/commit/38905c9) MAKECOMMAND is set by CTest.cmake and gets put in

Re: [CMake] Does a ctested build work with make -j

2014-01-28 Thread Bill Hoffman
On 1/28/2014 10:46 AM, Bill Hoffman wrote: MAKECOMMAND is set by CTest.cmake and gets put in the file that CTest reads to get the build command. If you set that make Experimental will work. If you note the change in the Sliicer github link you sent, you can see it sets

[CMake] Does a ctested build work with make -j

2014-01-27 Thread John Cary
It seems that after configuring with ctest enabled, make -j4 does 4 builds at once make ExperimentalStart ExperimentalBUild -j4 does only one build at a time. Is this behavior expected? Is there a way to get back to parallel builds when using ctest for the build? ThxJohn

Re: [CMake] Does a ctested build work with make -j

2014-01-27 Thread Bill Hoffman
On 1/27/2014 1:42 PM, John Cary wrote: It seems that after configuring with ctest enabled, make -j4 does 4 builds at once make ExperimentalStart ExperimentalBUild -j4 does only one build at a time. Is this behavior expected? Is there a way to get back to parallel builds when

Re: [CMake] Does a ctested build work with make -j

2014-01-27 Thread Matthew Woehlke
On 2014-01-27 17:12, Bill Hoffman wrote: On 1/27/2014 1:42 PM, John Cary wrote: It seems that after configuring with ctest enabled, make -j4 does 4 builds at once make ExperimentalStart ExperimentalBUild -j4 does only one build at a time. Is this behavior expected? Is there a