[CMake] ExternalProject danger- source directory is deleted

Jean-Christophe Fillion-Robin jchris.fillionr at kitware.com
Wed May 9 14:44:35 EDT 2012


Hi Pat,

In some extent, I think the problem has been addressed in CMake master. See


http://public.kitware.com/gitweb?p=cmake.git;a=commitdiff;h=987c017f6b1b49ab832c244166e30e07260432da

http://public.kitware.com/gitweb?p=cmake.git;a=commitdiff;h=987c017f6b1b49ab832c244166e30e07260432da
and
  http://www.cmake.org/Bug/view.php?id=12564

Hth
Jc

On Wed, May 9, 2012 at 2:32 PM, Pat Marion <pat.marion at kitware.com> wrote:

> When using ExternalProject, sometimes the build rules decide that an
> existing source directory needs to be deleted and re{downloaded,cloned}.
> In my experience, this is pretty dangerous and I have lost work due to it.
> Would it be possible to throw an error and ask the user to perform the
> delete, or pass a --force argument?  Is it the case that dashboards rely on
> the ability to do a hard-delete of a source directory during intermediate
> builds?
>
> Pat
>
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>



-- 
+1 919 869 8849
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20120509/c70151e7/attachment.htm>


More information about the CMake mailing list