On 8. Feb 2014, at 14:28, David Cole <[email protected]> wrote: > When you give a git repo for ExternalProject, it will *always* execute the > UPDATE_COMMAND by default. And then, all the steps after update will > re-execute since update re-ran.
We solved this by using a CMake script as an update step for autoconf projects, which does nothing if configure ran already: https://github.com/Eyescale/Buildyard/blob/master/CMake/UseExternalAutoconf.cmake#L26 Used here, which feeds into ExternalProject just below: https://github.com/Eyescale/Buildyard/blob/master/CMake/UseExternal.cmake#L320 HTH, Stefan. -- http://www.eyescale.ch https://github.com/Eyescale/ http://www.linkedin.com/in/eilemann
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 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://www.cmake.org/mailman/listinfo/cmake
