Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 3267655004d3f43eb14e0ea6a177bb09aaf19e65
commit3267655004d3f43eb14e0ea6a177bb09aaf19e65[log] [tgz]
authorPavel Salomatov <salomatovpavel@gmail.com>Wed Mar 06 20:00:45 2019 +0300
committerPavel Salomatov <salomatovpavel@gmail.com>Mon Mar 11 19:22:29 2019 +0300
treeb4dd7624bad6098a4354ef82c6bca779f425bbe2
parente34ff5ca5d1d5d9f138b2a3e59962d2b65b97c09 [diff]
releasetools: Add compatibility for custom out directory.

sign_target_files_apks script looks for the signapk.jar inside the out dir.
If the our dir is set to a different directory via OUT_DIR_COMMON_BASE the script does not work properly.

From now script checks if the OUT_DIR_COMMON_BASE is set, then searches the jar in the proper path.
If OUT_DIR_COMMON_BASE is unset, searches in "out" like it did before.

Test: Build with OUT_DIR_COMMON_BASE set and unset and verify that sign_target_files_apks works in both cases

Change-Id: I9218b98ff79526184f8353705640193405afac9e
1 file changed
tree: b4dd7624bad6098a4354ef82c6bca779f425bbe2
  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. envsetup.sh
  12. help.sh
  13. navbar.md
  14. OWNERS
  15. README.md
  16. tapasHelp.sh
  17. 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.