-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Base: implement KnownLocations for android #2353
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 please test |
@swift-ci test linux |
@swift-ci please test |
My proposal is: Let’s revert to the non-abort patch and mandate that people set |
(That way, they can source the internal storage path from an activity without us guessing.) |
This can be enforced by |
@swift-ci please test |
I also approve the environment variable approach (with the last comment by Lily implemented). |
Add a path through KnownLocations for android. This currently cannot be computed as we do not have the activity context nor do we know if the activity was spawned from the zygote or was a NDK process so we do not have a reference to Davlik to JNI and query the required information. This is sufficient to get the SDK building for android though.
@swift-ci please test |
While we’re using it directly here, it is also already picked up by CFPlatform.c, so API like NSHomeDirectory(), FileManager etc. will all heed it. |
Add support for android to KnownLocations. Assume that only current
user is supported as all applications in android are isolated and single
user. For now, place all files in ~/Apple/Library/Preferences. This is
the last piece needed in CoreFoundation for Android support.