Skip to content

Get SwiftSyntax ready for building in a unified build with other projects #167

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
Nov 4, 2019

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented Oct 31, 2019

Avoid recompiling SwiftSyntax for every project that depends on it by building all of these projects in a unified build.

This PR gets SwiftSyntax ready for the unified build by providing a --multiroot-data-file command line option with which the workspace for the unified build can be specified. Furthermore it sets environment variables that configure the builds of downstream jobs to use local dependencies.

See swiftlang/swift#28005

@ahoppen ahoppen requested review from akyrtzi and nkcsgexi October 31, 2019 23:04
@ahoppen
Copy link
Member Author

ahoppen commented Oct 31, 2019

@swift-ci Please test

env['SWIFT_SYNTAX_CI_ENVIRONMENT'] = '1'
env['SWIFT_BUILD_SCRIPT_ENVIRONMENT'] = '1'
# Tell other projects in the unified build to use local dependencies
env['SWIFTCI_USE_LOCAL_DEPS'] = '1'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need two environment variables instead of only one?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My idea was that someone would still be able to build a non-build-script build (i.e. static libraries, no enforce-exclusivity=unchecked) while still using the already checked out sources.

Similarly when building the stress tester you might want to create a CI-style build without manually checking out SwiftSyntax etc. You could do that by specifying --no-local-dependencies on the stress tester's build script.

It just feels like these are two different things that we should not mush together into a single flag.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, sounds good, but then should SWIFTCI_USE_LOCAL_DEPS have a more general name, like SWIFT_BUILD_USE_LOCAL_DEPS or something, and not seem like it should be only set by the CI system?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name needs to match the one used in the Swift package manager here to avoid it from pulling in remote dependencies. I could go and change it there first.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not important, the exact spelling doesn't matter much

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. I’ll just leave it as is for now then.

@ahoppen ahoppen requested a review from aciidgh November 1, 2019 17:57
@ahoppen ahoppen merged commit 91982c2 into swiftlang:master Nov 4, 2019
@ahoppen ahoppen deleted the unified-build branch November 4, 2019 00:35
adevress pushed a commit to adevress/swift-syntax that referenced this pull request Jan 14, 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.

2 participants