Use the correct svn revision in --build-llvm-next builds

Bug: http://b/149832468

They were set to the revision of the current stable release instead.

Test: build.py --build-llvm-next
Change-Id: I1c42d090e78d5bb15d9eeec65d0bcf2c9395c79b
3 files changed
tree: 2535bb562713587135e5645e80cf790e843035d9
  1. kernel-boot-tests/
  2. patches/
  3. test/
  4. .gitignore
  5. __init__.py
  6. AddressSanitizer.md
  7. android_version.py
  8. bisect_driver.py
  9. build.py
  10. compiler_wrapper.py
  11. mapfile.py
  12. merge_from_upstream.py
  13. MODULE_LICENSE_BSD_LIKE
  14. MODULE_LICENSE_MIT
  15. OWNERS
  16. PREUPLOAD.cfg
  17. README.md
  18. source_manager.py
  19. test_compiler.py
  20. update-binutils.py
  21. update-lldb-prebuilts.py
  22. update-prebuilts.py
  23. update_kernel_toolchain.py
  24. utils.py
  25. version.py
README.md

Android Clang/LLVM Toolchain

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).

Build Instructions

$ 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.

More Information

We have a public mailing list that you can subscribe to: android-llvm@googlegroups.com