ci: don't generate clang-tidy #24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Running |
jbangelo
approved these changes
Apr 18, 2022
|
Going to merge for now, still iterating on a long term solution here: swift-nav/cmake#109 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This prevents clang-tidy targets from generating a
.clang-tidyin the source dir. This is a temporary fix, long term fix is here: swift-nav/cmake#109. This is necessary forswiftnav-rsbuild since the release and publish process (validated bycargo release minor) wants to make sure that the build doesn't modify things outside of the build dir.