Skip to content

[6.0][Macros] Remove plugin related flags from toolchain Info.plist #72642

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

Merged
merged 1 commit into from
Mar 29, 2024

Conversation

rintaro
Copy link
Member

@rintaro rintaro commented Mar 27, 2024

Cherry-pick #72629 into relaese/6.0

  • Explanation: Swift.org toolchains used to have -external-plugin-path flags pointing XcodeDefault.xctoolchain. That was needed to use macro plugins in Apple SDK. But since Apple macro plugins are now in platform directories, this is not needed anymore. Also it was actively harmful because these options precede project's OTHER_SWIFT_FLAGS, which makes it difficult to override.
  • Scope: Macro plugins search paths in Swift.org toolchains.
  • Risk: Low. No code changes.
  • Testing: Tested locally with a PR toolchain
  • Issues: rdar://125498074
  • Reviewers: Owen Voorhees (@owenv) Konrad Malawski (@ktoso)

`-external-plugin-path` flags pointing XcodeDefault.xctoolchain were
needed to use macro plugins in Apple SDK. But since Apple macro plugins
are not in `.xctoolchain` anymore, these flags are useless.

rdar://125498074
(cherry picked from commit 5d48a5a)
@rintaro rintaro requested a review from a team as a code owner March 27, 2024 23:56
@rintaro rintaro changed the title [Macros] Remove plugin related flags from toolchain Info.plist [6.0][Macros] Remove plugin related flags from toolchain Info.plist Mar 27, 2024
@rintaro
Copy link
Member Author

rintaro commented Mar 27, 2024

@swift-ci Please test

@rintaro rintaro merged commit a172a42 into swiftlang:release/6.0 Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants