[CMake] Do build after GIT_TAG changed in ExternalProject_Add

[Cedric Doucet]

I don't know why but providing my own STAMP_DIR seems to solve the problem: 

STAMP_DIR  ${EXTERNAL_DIR}/eigen/stamp

Hope it helps!

Cédric


----- Mail original -----
> De: "David Cole via CMake" <cmake at cmake.org>
> À: "typ1232" <dummdoof-doof at web.de>
> Cc: cmake at cmake.org
> Envoyé: Jeudi 23 Avril 2015 13:51:06
> Objet: Re: [CMake] Do build after GIT_TAG changed in ExternalProject_Add
> 
> Hmmmmmm. I am seeing the same behavior you are, even with the older
> CMake 2.8.12.2 -- the update step does run, but steps after that,
> which are supposed to depend on update, are not re-running.
> 
> I think your intuitive expectation is correct, and that
> configure/build/install should run after changing the GIT_TAG. I
> cannot see (quickly/yet) where the problem is in the chain of
> ExternalProject custom commands...
> 
> There's a nagging thought bouncing around in my brain telling me
> there's something awfully familiar about this problem, and that I've
> seen it and solved it before, but I can't quite put my finger on it.
> 
> I must be forgetting something. And unfortunately, with the complexity
> of ExternalProject, it takes quite some time to dig into something
> deeply.
> 
> Is anybody else listening on this thread? Shouldn't changing the
> GIT_TAG value cause a re-configure+build+install of the
> ExternalProject....?
> 
> 
> David C.
> 
> 
> 
> 
> 
> On Mon, Apr 20, 2015 at 8:45 AM, typ1232 <dummdoof-doof at web.de> wrote:
> > Note that I changed CMAKE_ARGS, so the target is used that contains the
> > file
> > that was changed in the commit.
> >
> > CMAKE_ARGS "-DSAF_INTENTIONAL_COMPILE_WARNING=TRUE"
> >
> >
> >
> > --
> > View this message in context:
> > http://cmake.3232098.n2.nabble.com/Do-build-after-GIT-TAG-changed-in-ExternalProject-Add-tp7590299p7590317.html
> > Sent from the CMake mailing list archive at Nabble.com.
> > --
> >
> > 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
> --
> 
> 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
>