-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Build] Update SWIFT_TARGET_LIBRARY_NAME for swiftRuntime in new build. #78977
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -86,7 +86,7 @@ endif() | |
target_compile_definitions(swiftRuntime | ||
PRIVATE | ||
-DSWIFT_RUNTIME | ||
-DSWIFT_TARGET_LIBRARY_NAME=swiftRuntime | ||
-DSWIFT_TARGET_LIBRARY_NAME=swiftRuntimeCore | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is incorrect, this should be There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's not the only place it gets used, and it was being used with All I'm trying to fix here is the build breakage, and only by updating the spelling that I've changed, rather than doing something entirely new. |
||
$<$<BOOL:${BUILD_SHARED_LIBS}>:-DswiftCore_EXPORTS> | ||
$<$<BOOL:${SwiftCore_ENABLE_BACKTRACING}>:-DSWIFT_ENABLE_BACKTRACING> | ||
$<$<BOOL:${SwiftCore_ENABLE_OVERRIDABLE_RETAIN_RELEASE}>:-DSWIFT_STDLIB_OVERRIDABLE_RETAIN_RELEASE> | ||
|
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 believe this is the only part that actually needs changing here so that the compatibility header picks things up correctly. This is an object library that only contains C/C++, so there shouldn't be any conflict with parts from the old build. Given that the
Runtime
module depends on the overlay, it will have to be a separate "supplemental" library anyway.