| commit | 11ecca63f67a8e16aac9a0f4fd109786b8af1a1e | [log] [tgz] |
|---|---|---|
| author | Akhil Narang <me@akhilnarang.dev> | Mon Oct 05 17:57:47 2020 +0530 |
| committer | Jackeagle <jackeagle102@gmail.com> | Sat Dec 12 07:25:22 2020 +0100 |
| tree | 70928af10360c4d87a088f7a340a5eafd4a5273b | |
| parent | 8836d5d7bf2ecbb10c5d6382b02a4ef862d31167 [diff] |
releasetools: ota_from_target_files: fix build for A-Only dynamic devices not building vendor The function `HasVendorParition()` was moved inside `HasTrebleEnabled()` in 9276cf0226d341927d0a7e682a8db677e25ae5dd It also has a different implementation now `HasPartition()` which was used by it earlier is still present, using the same implementation, so use that directly Fixes the following error Traceback (most recent call last): File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/internal/stdlib/runpy.py", line 174, in _run_module_as_main File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/internal/stdlib/runpy.py", line 72, in _run_code File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/__main__.py", line 12, in <module> File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/internal/stdlib/runpy.py", line 174, in _run_module_as_main File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/internal/stdlib/runpy.py", line 72, in _run_code File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/ota_from_target_files.py", line 2300, in <module> File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/ota_from_target_files.py", line 2279, in main File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/ota_from_target_files.py", line 2019, in GenerateNonAbOtaPackage File "/home/akhil/eleven/out/host/linux-x86/bin/ota_from_target_files/ota_from_target_files.py", line 855, in WriteFullOTAPackage NameError: global name 'HasVendorPartition' is not defined Change-Id: I9bd4ebc9d6b103cfd572bfd5eacd3f7a5b1a661c Signed-off-by: Akhil Narang <me@akhilnarang.dev>
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.