Skip to content
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

Correctly add .swiftmodule directories to the search path. #1245

Conversation

brentleyjones
Copy link
Collaborator

If a propagated .swiftmodule is ever in a directory-based layout (Name.swiftmodule/$TARGET.swiftmodule), then we need to add the path to the directory containing the top-level module directory, not the path to the .swiftmodule directory itself.

PiperOrigin-RevId: 456263364
(cherry picked from commit 21580ea)

If a propagated `.swiftmodule` is ever in a directory-based layout (`Name.swiftmodule/$TARGET.swiftmodule`), then we need to add the path to the directory containing the top-level module directory, not the path to the `.swiftmodule` directory itself.

PiperOrigin-RevId: 456263364
(cherry picked from commit 21580ea)
@brentleyjones brentleyjones enabled auto-merge (rebase) June 21, 2024 12:54
brentleyjones referenced this pull request Jun 21, 2024
If a propagated `.swiftmodule` is ever in a directory-based layout (`Name.swiftmodule/$TARGET.swiftmodule`), then we need to add the path to the directory containing the top-level module directory, not the path to the `.swiftmodule` directory itself.

PiperOrigin-RevId: 456263364
@brentleyjones brentleyjones merged commit 31ca061 into master Jun 21, 2024
14 checks passed
@brentleyjones brentleyjones deleted the bj/correctly-add-.swiftmodule-directories-to-the-search-path branch June 21, 2024 12:57
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