Agreed, but right now ExternalProject is my favorite solution to this problem. I prefer the ExternalProject approach over the ParaView + internal VTK / git-submodule approach. So I'm just looking for ways to alter ExternalProject to be a little nicer to my workflow, which is incremental builds of multiple projects with project dependencies defined in a superbuild script.
Pat On Mon, Sep 16, 2013 at 12:23 PM, David Cole <dlrd...@aol.com> wrote: > ... 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. >> > > > Ahem. "If you modify a source file of a project" then *you* should rebuild > the project. > > ExternalProject does not now and never will handle inter-project > source-level dependencies properly (with minimal rebuilds). That's what > add_subdirectory and "interal projects" are all about. > > You can try to make EP do what you want, but .... if you are modifying > these things then they are NOT really "External." > > You can "Square peg. Round hole. Make it fit with brute force CMake code > anyway." as much as you want. > > But I wouldn't do that. > > > ;-) > D > >
-- 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
