Hi. The reason is to make build to fail as soon as possible if core library doesn't work properly. In C++ world that could be critical as hell because building process can last hours even on 32 cores.
And it will make CMake more ecological tool as it will reduce the energy wasted. :) On Jun 1, 2016, Magnus Therning <mag...@therning.org> wrote: > >Vladimir Chebotarev <vladimir.chebota...@gmail.com> writes: > >> Hi there. >> >> At the moment one can add a command executing after a build of a >target >> using: >> add_custom_command(... POST_BUILD...) >> >> However if the command have a dependencies which build after the >target, >> there is practically no way to specify it. >> >> Simple case: we have a library and tests for it. E.g. I want them to >run in >> POST_BUILD of a library. But, tests already depends on the library so >I >> can't make them built before it. >> >> There are few possible solutions to that: >> 1) add possibility to set dependencies for add_custom_command in >POST_BUILD >> mode; >> 2) add possibility to populate list of targets if we have specified >ones in >> list. >> >> Or maybe correct me if I miss something. > >Have you not simply missed add_test()? ;) > >What's the reason for wanting the tests to run post-build, rather than >on `make test`? > >/M Kind regards, Vladimir. -- 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
