Skip to content

stubs: avoid reaching up-tree, prefer inclusion options #40855

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 15, 2022

Conversation

compnerd
Copy link
Member

This removes the explicit tree structure reference in the stubs to
locate the shims. Instead, it expects that the SwiftShims directory
will be added to the header search path.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

This removes the explicit tree structure reference in the stubs to
locate the shims.  Instead, it expects that the `SwiftShims` directory
will be added to the header search path.
@compnerd
Copy link
Member Author

CC: @Azoy @mikeash @etcwilde

@compnerd
Copy link
Member Author

@swift-ci please test

Copy link
Member

@etcwilde etcwilde left a comment

Choose a reason for hiding this comment

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

Yes please!

Copy link
Contributor

@Azoy Azoy left a comment

Choose a reason for hiding this comment

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

❤️

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - ca39bb5

@etcwilde
Copy link
Member

OSX failure: The authorization was denied since no user interaction was possible.

@etcwilde
Copy link
Member

@swift-ci please test macOS

@compnerd compnerd merged commit 58d080a into swiftlang:main Jan 15, 2022
@compnerd compnerd deleted the search-order branch January 15, 2022 23:16
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.

5 participants