Skip to content

Swift-Syntax Prebuilts for Macros 6.1 #8214

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 3 commits into from
Jan 14, 2025

Conversation

dschaefer2
Copy link
Member

Following the pattern used for the early Traits work, added a workspace prebuilts manager to co-ordinate detecting when macros are using swift-syntax, downloading the zip file for the resolved swift-syntax version, and extracting it into the scratch directory. We add the necessary information about that to the workspace state. We then morph the Modules that use it to add build settings to find the necessary modules and libraries.

Cherry picked to 6.1 and a few fixes including ensuring we're only applying the prebuilts to macro targets.

dschaefer2 and others added 2 commits January 13, 2025 09:37
…#8142)

Following the pattern used for the early Traits work, added a workspace
prebuilts manager to co-ordinate detecting when macros are using
swift-syntax, downloading the zip file for the resolved swift-syntax
version, and extracting it into the scratch directory. We add the
necessary information about that to the workspace state. We then morph
the Modules that use it to add build settings to find the necessary
modules and libraries.

---------

Co-authored-by: Doug Schaefer <[email protected]>
Get set up for 6.1.

Also fix the build prebuilts script to not generate debug info.
That now breaks downstream consumers.
@dschaefer2 dschaefer2 merged commit 6f5330b into swiftlang:release/6.1 Jan 14, 2025
5 checks passed
@dschaefer2 dschaefer2 deleted the prebuilt-6.1 branch January 14, 2025 20:51
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.

2 participants