Skip to content

Commit 7c0d7d4

Browse files
committed
Update incorrect SDK name and CI link in doc to 5.8
1 parent 6182455 commit 7c0d7d4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ I will write up a Swift script to do this SDK configuration one day, but you
1616
will need to do it manually for now (I'll show aarch64 below, the same will
1717
need to be done separately for the armv7 or x86_64 json files).
1818

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`
2020
to point to the clang headers that come with your swift compiler, eg
2121

2222
```
@@ -66,7 +66,7 @@ You can copy these executables and the SDK to [an emulator or a USB
6666
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),
6767
or put them on an Android device with [a terminal emulator app like Termux](https://termux.dev/en/).
6868
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).
7070

7171
Copy the test executables to the same directory as the SDK:
7272
```

0 commit comments

Comments
 (0)