-
Notifications
You must be signed in to change notification settings - Fork 219
[-debug-module-path] Prefer the moduleOutputInfo.output path if avail… #2012
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
Conversation
|
@swift-ci test |
66c6b94 to
d9c3e6d
Compare
|
@swift-ci test |
…able. While testing the LLDB support for enhanced module tracking I noticed that the driver currently always uses a relative path for -debug-module-path, which is an obvious problem when compiling in a different directory, or if the swift module output is in a different path than the object file output. This patch addresses this by preferring moduleOutputInfo.output if available. rdar://164524241
d9c3e6d to
2ee2835
Compare
|
@swift-ci test |
|
Hmm |
|
@swift-ci test Windows platform |
|
@swift-ci test Windows platform |
|
Windows failed to CMake Docc... |
|
@swift-ci test windows |
3 similar comments
|
@swift-ci test windows |
|
@swift-ci test windows |
|
@swift-ci test windows |
|
@adrian-prantl Seems like the new assertion is failing on the CI now, would you mind taking a look? |
…able.
While testing the LLDB support for enhanced module tracking I noticed that the driver currently always uses a relative path for -debug-module-path, which is an obvious problem when compiling in a different directory, or if the swift module output is in a different path than the object file output. This patch addresses this by preferring
moduleOutputInfo.outputif available.rdar://164524241