commit | 308a247b524b67b814429e2fd5a05d978f11385f | [log] [tgz] |
---|---|---|
author | Yi Kong <yikong@google.com> | Thu Dec 17 02:01:00 2020 +0800 |
committer | Yi Kong <yikong@google.com> | Thu Dec 17 02:01:00 2020 +0800 |
tree | 145948a1f4b99b10f8c854a2f451a63855104041 | |
parent | c1d5c80463b38d6e43a4edc5c3d2a29499298ed9 [diff] |
Use llvm-lipo instead of system lipo Test: presubmit Change-Id: I1e328260d79beb30a4f5451b4ceb04e56db83716
For the latest version of this doc, please make sure to visit: Android Clang/LLVM Toolchain Readme Doc
You can also visit the Android Clang/LLVM Prebuilts Readme Doc for more information about our prebuilt toolchains (and what versions they are based upon).
$ mkdir llvm-toolchain && cd llvm-toolchain $ repo init -u https://android.googlesource.com/platform/manifest -b llvm-toolchain $ repo sync -c $ python toolchain/llvm_android/build.py
If building on Linux, pass --no-build windows
to build.py
to skip building Clang for Windows.
If you have an additional llvm tree built and present in your $PATH
, then build.py
might fail during the Windows build of libcxxabi with the error 'libstdc++ version must be at least 4.8.'
. The solution is to remove that path from your $PATH
before invoking build.py
.
To rebuild a particular toolchain, find the manifest file for that release:
$ $TOOLCHAIN_DIR/bin/clang -v Android (6317467 based on r365631c1) clang version 9.0.8...
The build number for that toolchain is 6317467
and the manifest is found in $TOOLCHAIN_DIR/manifest_6317467.xml
Rebuild the toolchain with that manifest:
$ mkdir llvm-toolchain && cd llvm-toolchain $ repo init -u https://android.googlesource.com/platform/manifest -b llvm-toolchain $ cp $TOOLCHAIN_DIR/manifest_6317467.xml .repo/manifests $ repo init -m manifest_6317467.xml $ repo sync -c # Optional: Apply any LLVM/Clang modifications to toolchain/llvm-project $ python toolchain/llvm_android/build.py
We have a public mailing list that you can subscribe to: android-llvm@googlegroups.com