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
Adds options to `configure` in a similar fashion and with similar
constraints to the options added in `swift` to add Android Support.
This will allow initially those features to be just passed from
`utils/build-script` without any change until a full strategy for
cross-compilation in all the involved projects is defined.
This is an example call to build for Android with Swift support:
```
env \
CC="${swift_android_path}/build/Ninja-ReleaseAssert/llvm-linux-x86_64/bi
n/clang" \
CXX="${swift_android_path}/build/Ninja-ReleaseAssert/llvm-linux-x86_64/b
in/clang++" \
SWIFTC="${swift_android_path}/build/Ninja-ReleaseAssert/swift-linux-x86_
64/bin/swiftc" \
${swift_android_path}/swift-corelibs-libdispatch/configure \
--with-swift-toolchain=“${swift_android_path}/build/Ninja-ReleaseAssert/
swift-linux-x86_64/" \
--with-build-variant=release \
--enable-android \
--host=arm-linux-androideabi \
--with-android-ndk=${ndk_path} \
--with-android-api-level=21 \
--disable-build-tests
```
* NOTE: `shims/android/lib(pthread|rt).a` were added to avoid modifying
`libpwq` and `libkqueue` submodules. This two projects are adding
`-lpthread -lrt` in `dependency_libs` at their libtool `la` files,
causing this to be extended until the final linking of the dynamic
library. There should be a more elegant solution to this issue.
0 commit comments