-
Notifications
You must be signed in to change notification settings - Fork 263
Facilitate implicit import of Dispatch in Foundation #201
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -200,13 +200,14 @@ def build(args): | |
libdispatch_args=libdispatch_args, | ||
source_paths=" ".join(sourcePaths))) | ||
run("{swiftc} -emit-library {build_dir}/XCTest.o " | ||
"-L {foundation_build_dir} -lswiftGlibc -lswiftCore -lFoundation -lm " | ||
"-L {dispatch_build_dir} -L {foundation_build_dir} -lswiftGlibc -lswiftCore -lFoundation -lm " | ||
# We embed an rpath of `$ORIGIN` to ensure other referenced | ||
# libraries (like `Foundation`) can be found solely via XCTest. | ||
"-Xlinker -rpath=\\$ORIGIN " | ||
"-o {build_dir}/libXCTest.so".format( | ||
swiftc=swiftc, | ||
build_dir=build_dir, | ||
dispatch_build_dir=os.path.join(args.libdispatch_build_dir, 'src', '.libs'), | ||
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. Totally in favor of this change, which makes this a little more explicit. Thanks! |
||
foundation_build_dir=foundation_build_dir)) | ||
|
||
# Build the static library. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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'll defer to @briancroom on this one. Does Android really not provide a
stdout
file handle? Is this a shortcoming in the Swift Glibc overlay when built for Android? If so, I guess I'm fine with 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.
Yeah, this is interesting! I dug a little bit and found that
stdout
isn't being build for Android currently: https://github.com/apple/swift/blob/48308411393e730cf3cb21d353a9be31045c47e4/stdlib/public/Platform/Platform.swift#L98And here's a bug about a Swift test failure caused by the same issue (guess who filed it? 🙃): https://bugs.swift.org/browse/SR-1835
It looks like these could be brought in only by building against Android API level 23, which may be an acceptable change at some point in the future.