Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 71b7f7fbd0aa95d0f026bdee8a061ae5a8c34055
commit71b7f7fbd0aa95d0f026bdee8a061ae5a8c34055[log] [tgz]
authorAnton Hansson <hansson@google.com>Thu Feb 21 11:36:37 2019 +0000
committerAnton Hansson <hansson@google.com>Thu Feb 21 14:32:13 2019 +0000
tree0c683269f839393f23a27d90667eebfe4170b628
parent30851f2540b354e7b8e97edb0b772d347c5a5f6b [diff]
Add support for *_CPU_VARIANT_RUNTIME flags

Specified in the BoardConfig, and default to the value of the non
_RUNTIME variants.

These flags do not modify build-time compilation, but get written to
system properties on /vendor and can be inspected at runtime to
run/compile code for the specified cpu.

Migrate the bionic and ART cpu variant flags to use the new variables,
but leave the ART preopting using the non-_RUNTIME variants.

Bug: 120773446
Test: boot downstream device specifying CPU_VARIANT_RUNTIME flags
Test: grep dalvik.vm vendor/default.prop
Change-Id: Idc81110172582f38f84cca87f2eff140c5b5f9ac
3 files changed
tree: 0c683269f839393f23a27d90667eebfe4170b628
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. buildspec.mk.default
  9. Changes.md
  10. CleanSpec.mk
  11. envsetup.sh
  12. help.sh
  13. navbar.md
  14. OWNERS
  15. README.md
  16. tapasHelp.sh
  17. Usage.txt
README.md

Android Make Build System

This is the Makefile-based portion of the Android Build System.

For documentation on how to run a build, see Usage.txt

For a list of behavioral changes useful for Android.mk writers see Changes.md

For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.

This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.