Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 40e55c20eb2598f5b628b1e8fce0328e7055fe88
commit40e55c20eb2598f5b628b1e8fce0328e7055fe88[log] [tgz]
authorUlya Trafimovich <skvadrik@google.com>Fri Mar 27 12:12:59 2020 +0000
committerUlya Trafimovich <skvadrik@google.com>Wed Jun 03 17:38:26 2020 +0100
tree45d6a11aa622135cdc9acc4f33397823d504a5ca
parent1c294551b4c229d8499ae419c8fcbf135769386e [diff]
Add product variable PRODUCT_BROKEN_SUBOPTIMAL_ORDER_OF_SYSTEM_SERVER_JARS.

If true, incorrect order of system server jars does not cause a build
error. The order is non-optimal if some jar X precedes its dependency Y.
In that case dexpreopt will be unable to resolve any rerefences from X
to Y.

Test: lunch cf_x86_phone-userdebug && m nothing
Test: lunch aosp_car_arm && m nothing

Bug: 140451054

Change-Id: I70efd365fa9fbd9e40792d646f8471d009164924
Merged-In: I70efd365fa9fbd9e40792d646f8471d009164924
(cherry picked from commit 17715b48f0e25b5d28d3d51660262b023eb48731)
2 files changed
tree: 45d6a11aa622135cdc9acc4f33397823d504a5ca
  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. Deprecation.md
  12. envsetup.sh
  13. help.sh
  14. navbar.md
  15. OWNERS
  16. rbesetup.sh
  17. README.md
  18. tapasHelp.sh
  19. 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.