Skip to content

build: add additional target exports for static linking #496

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
Jan 23, 2025

Conversation

compnerd
Copy link
Member

When building tools-support-core using statically linked libraries, we need to export additional targets to ensure that the full closure is available to consumers.This is meant to support building swift-driver against a statically linked form of tools-support-core to allow using the early swift-driver on Windows.

When building tools-support-core using statically linked libraries, we
need to export additional targets to ensure that the full closure is
available to consumers.This is meant to support building swift-driver
against a statically linked form of tools-support-core to allow using
the early swift-driver on Windows.
@MaxDesiatov
Copy link
Contributor

@swift-ci test

@compnerd
Copy link
Member Author

@swift-ci please test Linux platform

1 similar comment
@compnerd
Copy link
Member Author

@swift-ci please test Linux platform

@compnerd compnerd merged commit bd9e2de into swiftlang:main Jan 23, 2025
3 checks passed
@compnerd compnerd deleted the exports branch January 23, 2025 19:44
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