Google Git
Sign in
android / platform / build / 36b659550e151611394912bcd2f70e1dcb4d9dc7
commit36b659550e151611394912bcd2f70e1dcb4d9dc7[log] [tgz]
authorDevin Moore <devinmoore@google.com>Fri Jun 18 08:22:50 2021 -0700
committerDevin Moore <devinmoore@google.com>Mon Jun 21 12:48:24 2021 -0700
tree2ff9542c98b866760c806c6610170b4b4953073a
parent122a00734beea20dc9912bde1cfaac4fab349feb [diff]
Revert "Throw an error if androidboot.hardware is used for bootconfig"

This reverts commit 2e43e34d535ad9030885be9f5942d0c29f569c2e.

The kernel bootconfig feature has been updated to handle mixed subkeys
and values, so androidboot.hardware is ok to use now.

Test: build and boot cuttlefish with 'hardware=cutf_vm'
Test: build and boot cuttlefish with 'androidboot.hardware=cutf_vm'
Bug: 191502832
Merged-In: I7c3f330a73abe6cf1fb7d14aaaa6cbc3e874a4aa
Change-Id: I7c3f330a73abe6cf1fb7d14aaaa6cbc3e874a4aa
1 file changed
tree: 2ff9542c98b866760c806c6610170b4b4953073a
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. Android.bp
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. Deprecation.md
  14. envsetup.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. tapasHelp.sh
  23. 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.