You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ I will write up a Swift script to do this SDK configuration one day, but you
16
16
will need to do it manually for now (I'll show aarch64 below, the same will
17
17
need to be done separately for the armv7 or x86_64 json files).
18
18
19
-
Change the symbolic link at `swift-5.8.1-android-24-sdk/usr/lib/swift/clang`
19
+
Change the symbolic link at `swift-5.8-android-24-sdk/usr/lib/swift/clang`
20
20
to point to the clang headers that come with your swift compiler, eg
21
21
22
22
```
@@ -66,7 +66,7 @@ You can copy these executables and the SDK to [an emulator or a USB
66
66
debugging-enabled device with adb](https://github.com/apple/swift/blob/release/5.8/docs/Android.md#3-deploying-the-build-products-to-the-device),
67
67
or put them on an Android device with [a terminal emulator app like Termux](https://termux.dev/en/).
68
68
I test aarch64 with Termux so I'll show how to run the test runner there, but
69
-
the process is similar with adb, [as can be seen on the CI](https://github.com/buttaface/swift-android-sdk/blob/5.7.1/.github/workflows/sdks.yml#L326).
69
+
the process is similar with adb, [as can be seen on the CI](https://github.com/buttaface/swift-android-sdk/blob/5.8/.github/workflows/sdks.yml#L326).
70
70
71
71
Copy the test executables to the same directory as the SDK:
0 commit comments