> From: Eric Noulard [mailto:eric.noul...@gmail.com] > Sent: Wednesday, July 01, 2015 6:14 PM > To: Honggyu Kim > Cc: CMake Developers > Subject: Re: [cmake-developers] dry-run support
> What you already have with CMake is the --trace option which can be very > useful > to understand what happen at CMake time. I will try --trace option later. > Then it may also be useful to dry-run the resulting build files produced by > CMake. > i.e.: > make --dry-run > ninja -n -v > ... You're right. There's no such dry-running in CMake and it just generates the normal Makefile. I got the list of execution commands by running dry-run on generated Makefile with --dry-run and --always-make options. --always-make forces to show the entire command list regardless it is already compiled or not. So my problem is solved anyway. > -- > Eric I appreciate your comment. Thanks, Honggyu -- 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
