search for: externalproject_add_step

...to re-run CMake if any of the inputs have > > changed. > > > > Suppose LLVMConfig.cmake has changed. > > Every file CMake processes as part of configuring the project ends up in > the build-time dependencies to re-run CMake. > Alright, I've switched this to ExternalProject_Add_Step(compiler-rt force-rebuild DEPENDERS build ALWAYS 1 ) However, looks like this works with Unix Makefiles generators, but doesn't work for Ninja. When I run "ninja compiler-rt" twice in the build tree, I see the following message on the second run: ninja: no work to do. I...

Hi Brad, I have a few questions regarding ExternalProject_Add. For me it doesn't really work as expected. I add the following code to the tools/clang/runtime/CMakeLists.txt to configure compiler-rt as external project: ExternalProject_Add(compiler-rt #DEPENDS clang clang++ llvm-config PREFIX ${CMAKE_BINARY_DIR}/projects/compiler-rt SOURCE_DIR ${COMPILER_RT_SRC_ROOT}

On Mon, Feb 24, 2014 at 6:57 PM, Brad King <brad.king at kitware.com> wrote: > On 02/24/2014 09:44 AM, Alexey Samsonov wrote: > > ExternalProject_Add_Step(compiler-rt force-rebuild > > DEPENDERS build > [snip] > > doesn't work for Ninja. > > What version of CMake did you use for this test? Also 2.8.10? > Yes, 2.8.10.2 to be exact. > > > Is it a CMake bug? > > Yes, though there have been some changes...

On Fri, Feb 21, 2014 at 9:03 PM, Brad King <brad.king at kitware.com> wrote: > On 02/21/2014 11:20 AM, Alexey Samsonov wrote: > > We can even use "DEPENDERS configure" instead of "DEPENDERS build" here. > > Just "build" should be sufficient because the generated build system > in compiler-rt knows how to re-run CMake if any of the inputs have

...velopment then occurs in > each tree manually. > > Using ExternalProject for a recursive-make-like structure was > only later proposed as a use case. In order to make the build > step always run you need to make it depend on an extra step that > is always out of date: > > ExternalProject_Add_Step(compiler-rt always-build > COMMENT "Always building MyCOnly..." > DEPENDERS build > ALWAYS 1 > ) > Great, thanks for suggestion! We can even use "DEPENDERS configure" instead of "DEPENDERS build" here. And we'd better "clobber" th...

...passed through like this? > The set seems somewhat arbitrary, but I may be missing something > obvious. > > > ${ARG_CMAKE_ARGS} > > ${PASSTHROUGH_VARIABLES} > > INSTALL_COMMAND "" > > @@ -152,7 +165,7 @@ > > ExternalProject_Add_Step(${name} force-rebuild > > COMMAND ${run_build} > > COMMENT "Forcing rebuild of ${name}" > > - DEPENDEES configure clean > > + DEPENDEES configure ${always_clean} > > I'm not sure I understand what this does. If I had to guess I...

...bitrary, but I may be missing something >>> obvious. >>> >>> > ${ARG_CMAKE_ARGS} >>> > ${PASSTHROUGH_VARIABLES} >>> > INSTALL_COMMAND "" >>> > @@ -152,7 +165,7 @@ >>> > ExternalProject_Add_Step(${name} force-rebuild >>> > COMMAND ${run_build} >>> > COMMENT "Forcing rebuild of ${name}" >>> > - DEPENDEES configure clean >>> > + DEPENDEES configure ${always_clean} >>> >>> I'm not sure I u...

...> obvious. >>>>> >>>>> > ${ARG_CMAKE_ARGS} >>>>> > ${PASSTHROUGH_VARIABLES} >>>>> > INSTALL_COMMAND "" >>>>> > @@ -152,7 +165,7 @@ >>>>> > ExternalProject_Add_Step(${name} force-rebuild >>>>> > COMMAND ${run_build} >>>>> > COMMENT "Forcing rebuild of ${name}" >>>>> > - DEPENDEES configure clean >>>>> > + DEPENDEES configure ${always_clean} >>>&gt...