Skip to content

Conversation

@adrian-prantl
Copy link
Contributor

…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

@adrian-prantl
Copy link
Contributor Author

@swift-ci test

@adrian-prantl adrian-prantl force-pushed the eng/PR-164524241 branch 3 times, most recently from 66c6b94 to d9c3e6d Compare November 14, 2025 00:29
@adrian-prantl
Copy link
Contributor Author

@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
@adrian-prantl
Copy link
Contributor Author

@swift-ci test

@adrian-prantl
Copy link
Contributor Author

Hmm testEmitClangHeaderMinAccess seems to also fail with my patch reverted.

@artemcm
Copy link
Contributor

artemcm commented Nov 14, 2025

@swift-ci test Windows platform

@adrian-prantl
Copy link
Contributor Author

@swift-ci test Windows platform

@adrian-prantl
Copy link
Contributor Author

Windows failed to CMake Docc...

@adrian-prantl
Copy link
Contributor Author

@swift-ci test windows

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.

4 participants