Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 5fe287beb4e3012d73a87346fd56d6811ac453f5
commit5fe287beb4e3012d73a87346fd56d6811ac453f5[log] [tgz]
authorTao Bao <tbao@google.com>Thu Oct 11 14:13:52 2018 -0700
committerTao Bao <tbao@google.com>Thu Oct 11 14:39:09 2018 -0700
tree253ec817b6757c48a3b0d894f5e29dcb8f594cd8
parentbb0d85169f94a993fbcd779624cd0848aaeb263a [diff]
releasetools: Rename test names in test_verity_utils.py.

There's a naming convention between the testcase and the class/method
being tested.

Also remove VerifiedBootVersion2HashtreeInfoGenerator as it's merely a
placeholder without telling anything much (e.g. whether it's to be
implemented or working as intended).

Test: python -m unittest test_verity_utils
Change-Id: Ieb156765c865aa551e3882f381e3a6db2cac4cbc
2 files changed
tree: 253ec817b6757c48a3b0d894f5e29dcb8f594cd8
  1. core/
  2. target/
  3. tests/
  4. tools/
  5. .gitignore
  6. Android.mk
  7. buildspec.mk.default
  8. Changes.md
  9. CleanSpec.mk
  10. envsetup.sh
  11. help.sh
  12. navbar.md
  13. OWNERS
  14. README.md
  15. tapasHelp.sh
  16. 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.