From c58f5e116e0fd4fd883320812bfb052582005e90 Mon Sep 17 00:00:00 2001 From: Bartosz Kosiorek Date: Fri, 15 Mar 2019 14:14:03 +0100 Subject: ExternalProject: Extend documentation about GIT_TAG usage When GIT_SHALLOW is used, the '--depth 1 --no-single-branch' arguments are add. It means that only branch names and tags is downloaded to repository. Most Commit Hash is not working. With this commit the documentation was updated, to describe the limitation of GIT_SHALLOW. --- Modules/ExternalProject.cmake | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Modules/ExternalProject.cmake b/Modules/ExternalProject.cmake index 96250d3..4344bdb 100644 --- a/Modules/ExternalProject.cmake +++ b/Modules/ExternalProject.cmake @@ -251,6 +251,9 @@ External Project Definition The lack of such deterministic behavior makes the main project lose traceability and repeatability. + If ``GIT_SHALLOW`` is enabled then ``GIT_TAG`` works only with + branch names and tags. A commit hash is not allowed. + ``GIT_REMOTE_NAME `` The optional name of the remote. If this option is not specified, it defaults to ``origin``. -- cgit v0.12