| commit | b4ec6d752afe61fd7d22cee64c85c281a801ba73 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Thu Mar 15 23:21:28 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Wed Mar 21 21:15:59 2018 +0000 |
| tree | 9e80d999b2b9cd92fbdd28c9770ccab9ef99dd2e | |
| parent | 2ebcf419e46cb7c77532feeea9aee3ac59f18d69 [diff] |
Remove the hard-coded path of build_verity_metadata.py. build_image.py used to invoke build_verity_metadata.py with a hard-coded path of 'system/extras/verity/build_verity_metadata.py', which makes it hard to run unittests from non-$(ANDROID_BUILD_TOP) directory. This CL adds the dependency on the tool, so that it gets installed to $(HOST_OUT_EXECUTABLES), then removes the hard-coded path. Bug: 74544459 Bug: 76015688 Test: `m dist` Test: python -m unittest test_validate_target_files Change-Id: I0dcf4eb067a0db6f099cb589eb99a151a05c7f2b
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.