On 03/12/2016 08:04 AM, Ruslan Baratov via cmake-developers wrote: > I guess it is a well known fact that cmake command is almost never > executed alone and for non-trivial examples usually hold some extra > arguments (home directory, build directory, verbosity level, toolchains, > options, ...). Also I guess that such commands doesn't change from > day-to-day development process and an obvious way to reduce typing is to > create wrapper build scripts (.bat or .sh, I personally use a Python one).
Sorry, I don't think something like this belongs upstream. It can easily be done with shell aliases or other custom scripts. We shouldn't increase the complexity of the CMake command line interface further. -Brad -- 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
