[CMake] Unnecessary rebuild of ExternalProject_Add target

[Jack Smith]

On Sat, Feb 8, 2014 at 2:55 PM, Stefan Eilemann <eilemann at gmail.com> wrote:

>
> On 8. Feb 2014, at 14:28, David Cole <dlrdave at aol.com> 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
>
>
>
>
> I tried the UPDATE_COMMAND solution proposed, and it had no effect on the
behavior.

[ 28%] Performing update step for 'grub'
Already on 'master'
Your branch is up-to-date with 'origin/master'.
[ 31%] Performing configure step for 'grub'
Importing unicode...
Importing libgcrypt...
.....

rebuild was performed unnecessarily.

What am I doing wrong ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20140209/c8f854b4/attachment.html>