commit | 5e612035111cb9f4abad43697350d4ea644fce33 | [log] [tgz] |
---|---|---|
author | Stephen Hines <srhines@google.com> | Thu Oct 10 12:25:42 2019 -0700 |
committer | Stephen Hines <srhines@google.com> | Thu Oct 10 13:58:55 2019 -0700 |
tree | 224c93815a22deb2e0f39d4d1a143e33f48a1d0a | |
parent | aa6c17fabaf5ceb3d1fca03a2cce57ecc3afd1bc [diff] |
Remove .cmake files from our package. Shipping .cmake files in the final package means that they might accidentally be picked up by other developer builds/tooling. We don't provide many of the .a files mentioned in these .cmake files, so this could result in unexpected build failures. Removing these files is the simplest solution, since we didn't really intend to provide them. Bug: 142327416 Test: Check for .cmake files in outputs after running ./build.py Change-Id: Iaae3f3494d371f3ad0e3d13f701f843d9d48117f
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
.
We have a public mailing list that you can subscribe to: android-llvm@googlegroups.com