Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 97c140ccadbf372770badacbdb1590e72b9648ba
commit97c140ccadbf372770badacbdb1590e72b9648ba[log] [tgz]
authorJustin Yun <justinyun@google.com>Tue Nov 15 18:20:12 2022 +0900
committerJustin Yun <justinyun@google.com>Tue Nov 15 18:20:12 2022 +0900
tree3866c6d5f14b38027c1ef5622028661eeb97d099
parent15b02bd17df150917c3cc1b8c24d1f3367f7f317 [diff]
Define vendor-hwasan-snapshot target

By building vendor-hwasan-snapshot target, static hwasan libraries
for vendor image variants will be snapshoted.
The list of candidate libs must be listed in
PRODUCT_VSDK_HWASAN_STATIC_PATHS with module name and source directory
path separated by colon.

For example,
PRODUCT_VSDK_HWASAN_STATIC_PATHS := \
  libbase:system/libbase \
  libc++_static:external/libcxx

Bug: 234772527
Test: SANITIZE_TARGET=hwaddress m vendor-hwasan-snapshot
Change-Id: Ic179740ae3bc8f90d2c5bbca7289ea72262ba8aa
1 file changed
tree: 3866c6d5f14b38027c1ef5622028661eeb97d099
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. finalize-aidl-vndk-sdk-resources.sh
  15. finalize-cleanup.sh
  16. finalize-step-1.sh
  17. finalize_branch_for_release.sh
  18. help.sh
  19. METADATA
  20. navbar.md
  21. OWNERS
  22. PREUPLOAD.cfg
  23. rbesetup.sh
  24. README.md
  25. tapasHelp.sh
  26. 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.