> What about instead of "cd path && ninja", using "ninja -C path"?
I suppose we can also change "cmake --build path", to use "ninja -C path" instead of "cd path && ninja", but making ninja always use full paths for source files would have these benefits: 1. consistency with make (as pointed out by Brad) 2. consistency regardless of where the build directory is located (in source, under source, or out of source) 3. all three ways of invoking the build would work for IDEs (cmake --build, cd && ninja, ninja -C), so future IDE writers won't run into the sample problem no matter which way they choose On Wed, Aug 3, 2016 at 1:12 PM, Ben Boeckel <ben.boec...@kitware.com> wrote: > On Wed, Aug 03, 2016 at 11:11:45 -0700, Chaoren Lin wrote: > > Also, in the case of vim, the makeprg is user-supplied, so vim has no > idea > > that it contains a path. > > What about instead of "cd path && ninja", using "ninja -C path"? > > --Ben >
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
