-
Notifications
You must be signed in to change notification settings - Fork 198
[BridgingHeader] Provide a deterministic unique pch file path #1567
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
[BridgingHeader] Provide a deterministic unique pch file path #1567
Conversation
@artemcm let me know what you think about this. The dependency scanner is not yet returning the context hash for main module but that can be easily added. |
@@ -1779,7 +1781,7 @@ extension Driver { | |||
/// The swift-driver doesn't have actions, so the logic here takes the jobs and tries | |||
/// to mimic the actions that would be created by the C++ driver and | |||
/// prints them in *hopefully* the same order. | |||
private func printActions(_ jobs: [Job]) { | |||
private mutating func printActions(_ jobs: [Job]) { |
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.
Why this change?
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.
Using lazy var
is mutating as I just learnt about it too.
8b7a7b0
to
14a8d8e
Compare
@swift-ci please test |
14a8d8e
to
c7f8a22
Compare
@swift-ci please test |
@swift-ci please test windows platform |
Teach swift driver to use a deterministic path for compiled PCH output. Also when dependency scanner is updated to return a module scanning or PCH hash from the scanning result, it will add that to the code path to have an unique PCH file path for the specific compilation.
c7f8a22
to
bb3eed3
Compare
@swift-ci please test |
@swift-ci please test windows |
Teach swift driver to use a deterministic path for compiled PCH output. Also when dependency scanner is updated to return a module scanning or PCH hash from the scanning result, it will add that to the code path to have an unique PCH file path for the specific compilation.