Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 4d6b38c47a5daec6896924310da1b6bfe75ff8a9
commit4d6b38c47a5daec6896924310da1b6bfe75ff8a9[log] [tgz]
authorYifan Hong <elsk@google.com>Wed Aug 01 16:44:43 2018 -0700
committerYifan Hong <elsk@google.com>Wed Aug 01 16:46:16 2018 -0700
tree27120591c5a9951d5680a5f328aca474c2f51d35
parentc0213682b3a2063b2ac0bbf399d42cfb2ba7a40e [diff]
target_files: copy to PRODUCT-SERVICES instead

The add_img_to_target_files.py script uses upper() to determine
the name of sub-directory under target_files_intermediates. The
name of the image is product-services.img but the sub-directory
name was PRODUCT_SERVICES. Change it to PRODUCT-SERVICES so that
'm dist' works.

Test: m dist
Change-Id: I8cad841c674b5d62c1d803d0383fc3aee14f272a
2 files changed
tree: 27120591c5a9951d5680a5f328aca474c2f51d35
  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.