I was using add_custom_command to execute three commands, triggering that rule with add_custom_target, and it worked great with make and ninja on linux and mac. Over on Windows, though, with visual c++ 2013 and cmake 3.0.1, only the first of the three commands was executed.
After much head-scratching, I junked the add_custom_targets, and just used add_custom_target, since the commands were supposed to be unconditional anyway. (Why'd I use add_custom_command in the first place?) That seemed to work better. (I also moved the three commands out into a script, which may also have helped.) Has anyone else had problems with add_custom_command being squirrely with visual c++? -- 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
