On Wed, May 25, 2016 at 11:47:25AM -0700, Ben Webb wrote: > On 5/23/16 1:58 PM, Tru Huynh wrote: > >I am preparing the computer lab machine for a course this summer > >and I am running into a strange "ninja issue". > ... > >CMake Error: CMake was unable to find a build program corresponding > >to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a > >different build tool. > > Odd, but this certainly looks like a cmake/ninja issue, nothing > IMP-specific. You might need to explicitly set CMAKE_MAKE_PROGRAM - > I think cmake only looks in /usr/bin/ for ninja. Alternatively, make > a minimal CMakeLists.txt that demonstrates the problem and report it > to the cmake folks.
Thanks for your reply.
cmake for CentOS-7 is 2.8.11, and it fails event with the basic oneline CMakeLists.txt (even if I export CMAKE_MAKE_PROGRAM=/.../ninja-1.7.1/ninja):
$ echo 'project(TOTO)' > CMakeLists.txt $ cmake . -G Ninja CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool. ....
If I use the cmake3 (cmake 3.5.2) from EPEL instead that works: $ cmake3 . -G Ninja -- The C compiler identification is GNU 4.8.5 -- The CXX compiler identification is GNU 4.8.5 ... -- Build files have been written to: /tmp/tmp.gfrIX6M2A7
Bottom line, use cmake3 for IMP :D
RFE for IMP CMakeLists.txt: cmake_minimum_required(VERSION 2.8.3) -> cmake_minimum_required(VERSION 3.0) ?
Best regards
Tru