Suppress CMake 'update' step in external projects #8
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.
When using a GIT_REPOSITORY source for a CMake external project, CMake performs an "update" step whenever the external project is evaluated. The idea is to update to the latest ref of the branch prior to invoking the configure/build/install commands, ensuring the target is fully up-to-date.
There are two reasons we want to suppress this step here:
This is the same pattern we're using in the various vendor packages under the ros2 org on GitHub, for example: ros2/mimick_vendor#17