-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Backtracing] Add support for building target executables into libexec. #63978
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
We're going to add a program, `swift-backtrace`, that gets built alongside the stdlib and the runtime, and that needs to be installed in libexec/swift alongside the libraries in lib/swift. It wants to be built with the stdlib/runtime because there's an internal interface between `swift-backtrace` and the runtime, so the program needs to stay in lock-step with the runtime library. rdar://105390807 (This reverts commit f042ca0.)
… targets. I missed off an `${sdk}` in the target name for the lipo'd output :-( rdar://105390807
`THIN_INPUT_TARGETS` needed to be reset per-sdk, not just once. rdar://105390807
@swift-ci Please test |
The original attempt at this was #63650. Unfortunately there were a couple of bugs that caused the build to fail if we were building for more than one SDK at once, so that one got reverted. |
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.
Overall LGTM, but IMO there are a few places that could benefit from added comments that explain the context for these changes.
I think that this inadvertently is impacting the Windows builds:
|
That should be fixed by #64010. Hopefully. |
We're going to add a program,
swift-backtrace
, that gets built alongside the stdlib and the runtime, and that needs to be installed in libexec/swift alongside the libraries in lib/swift.It wants to be built with the stdlib/runtime because there's an internal interface between
swift-backtrace
and the runtime, so the program needs to stay in lock-step with the runtime library.rdar://105390807