There's a related issue, I think, if you skip the update step, then the
project never rebuilds, since reconfigure and rebuild depend on update. So
if you modify a source file of a project without a download command, then
superbuild will not rebuild the project. So my workaround (used in VES,
for example) looks like this:
macro(force_build proj)
ExternalProject_Add_Step(${proj} forcebuild
COMMAND ${CMAKE_COMMAND} -E remove ${base}/Stamp/${proj}/${proj}-build
DEPENDEES configure
DEPENDERS build
ALWAYS 1
)
endmacro()
ExternalProject_Add(myproject
DOWNLOAD_COMMAND ""
....)
force_build(myproject)
I guess I could modify my force_build macro so only make re-runs, not
configure && make.
Pat
On Mon, Sep 16, 2013 at 11:59 AM, David Cole <dlrd...@aol.com> wrote:
> It *could* work, depending on the project.
>
> I wouldn't do it.
>
> But it *could* work.
>
>
--
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
