-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix -fmodule-map-file
pointing to non-existent path
#3247
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
Fix -fmodule-map-file
pointing to non-existent path
#3247
Conversation
@swift-ci please smoke test |
Tested locally to verify that this fixes the issue mentioned in #3246 |
This is for testing swiftlang/swift-package-manager#3247
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change LGTM. Does this have a unit test that should be extended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I verified that this fixes the error I was seeing locally. Need to wait for CI (swiftlang/swift#35202) to see if it fixes the build issue we saw with the source compat suite in swiftlang/swift#35503.
We should probably add a test, I was just trying to have a PR up quickly. |
@neonichu looks like a test needs to be updated? |
Looks like the test is correct, but the fix isn't. We still need to impart for Swift targets. The only case where we shouldn't is for clang targets with an explicit module map. |
We were passing this unconditionally which would break in the case where we weren't generated a module map because an explicit one exists. rdar://74115399
af0ad46
to
9a2fdbc
Compare
@swift-ci please smoke test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code changes seems reasonable, not familiar with the business logic tho
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, and agree that a test can follow in a separate PR in the interest of quickly fixing this.
We were passing this unconditionally which would break in the case where we weren't generated a module map because an explicit one exists.
rdar://74115399