Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / build / 8bc963530431fd59a955c310f351a8f5d47046e5
commit8bc963530431fd59a955c310f351a8f5d47046e5[log] [tgz]
authorJustin Yun <justinyun@google.com>Tue Nov 09 23:09:52 2021 +0900
committerJustin Yun <justinyun@google.com>Thu Nov 11 10:18:27 2021 +0900
tree52e21d87bb20774dbf9cafc0b7381db541f6d842
parente8722033647767aeb92896b93c66a79b47a639be [diff]
Fix BOARD_SYSTEMSDK_VERSIONS checks

BOARD_SYSTEMSDK_VERSIONS must be greater than or equal to the minimum
of PRODUCT_SHIPPING_API_LEVEL and BOARD_API_LEVEL. If BOARD_API_LEVEL
is not defined, read BOARD_SHIPPING_API_LEVEL. If both board api
levels are not defined, compare only with PRODUCT_SHIPPING_API_LEVEL.

Bug: 204964200
Bug: 201489975
Bug: 202919753
Test: manual test with different settings
Change-Id: I36fa0b2fed3bca9ebe1baad46ee1dbe8cb1414e3
(cherry picked from commit e81ec6960a64077cb46983499e80bdcc2dc316e2)
2 files changed
tree: 52e21d87bb20774dbf9cafc0b7381db541f6d842
  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.