-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.9] Run build tool plugins for C-family targets #6540
Merged
neonichu
merged 1 commit into
release/5.9
from
run-build-tool-plugins-for-c-family-targets-5.9
May 11, 2023
Merged
[5.9] Run build tool plugins for C-family targets #6540
neonichu
merged 1 commit into
release/5.9
from
run-build-tool-plugins-for-c-family-targets-5.9
May 11, 2023
Conversation
This file contains 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
@swift-ci please smoke test |
tomerd
changed the title
Run build tool plugins for C-family targets
[5.9] Run build tool plugins for C-family targets
May 11, 2023
tomerd
approved these changes
May 11, 2023
neonichu
force-pushed
the
run-build-tool-plugins-for-c-family-targets-5.9
branch
from
May 11, 2023 01:00
c410c4f
to
2a48ba4
Compare
@swift-ci please smoke test |
@swift-ci please smoke test windows |
neonichu
commented
May 11, 2023
tomerd
approved these changes
May 11, 2023
While we intentionally don't support generating C sources from plugins today since we haven't figured out how to deal with headers etc, not running plugins at all without any diagnostics whatsoever seems like an implementation oversight based on the fact that we have two completely different implementations for Swift and C-family targets (which is something we also need to rectify at some point). With this change, we're running build-tool plugins in the exact same way as we are doing it for Swift targets. We are only doing this for packages with tools-version 5.9 or higher in order to have any unintentional impact on existing packages. rdar://101671614 Co-authored-by: Max Desiatov <[email protected]> (cherry picked from commit 678e683)
neonichu
force-pushed
the
run-build-tool-plugins-for-c-family-targets-5.9
branch
from
May 11, 2023 17:42
2a48ba4
to
89830ec
Compare
@swift-ci please smoke test |
@swift-ci please smoke test windows |
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.
While we intentionally don't support generating C sources from plugins today since we haven't figured out how to deal with headers etc, not running plugins at all without any diagnostics whatsoever seems like an implementation oversight based on the fact that we have two completely different implementations for Swift and C-family targets (which is something we also need to rectify at some point).
With this change, we're running build-tool plugins in the exact same way as we are doing it for Swift targets. We are only doing this for packages with tools-version 5.9 or higher in order to have any unintentional impact on existing packages.
rdar://101671614
Co-authored-by: Max Desiatov [email protected]
(cherry picked from commit 678e683)