googletest.cmake: remove GIT_SHALLOW when cloning #9712
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #9705, the googletest dependency was changed from downloading a release version to cloning the git repository at a pinned commit from HEAD. To optimize this, the
GIT_SHALLOW
argument was specified to cmake'sExternalProject_Add()
function. This caused the cloned repository to have a different head commit SHA and confused cmake. To fix this, I just removed theGIT_SHALLOW
argument since the repository is pretty small and doing a deep clone is not that expensive.#no-changelog