Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / c747c3419ff4f7248da7cd84cdadfc2c405ef557
commitc747c3419ff4f7248da7cd84cdadfc2c405ef557[log] [tgz]
authorRonald Braunstein <rbraunstein@google.com>Tue Aug 22 15:39:19 2023 -0700
committerRonald Braunstein <rbraunstein@google.com>Tue Aug 22 16:02:04 2023 -0700
tree49e231b390546d904f08ad49b950f3902cb97eb3
parent1c950f7a766f11f893b437c54b006492b2d14fc2 [diff]
Add adevice_fingerprint to eng builds.

We are working on a replacement for "adb sync" and it requires something
running on the device to send back a fingerprint of the filesystem.
This binary is intendend to be part of developers going forward so we
are adding it in all eng/userdebug builds.
The binary is 830k bytes.

Test: m install-clean ; m ; acloud create --local-image ; adb shell ls -l /system/bin/adevice_fingerprint

Change-Id: I98359cc37cffeffc7ffbfd61d6bc9a51ba318a99
1 file changed
tree: 49e231b390546d904f08ad49b950f3902cb97eb3
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. help.sh
  15. METADATA
  16. navbar.md
  17. OWNERS
  18. PREUPLOAD.cfg
  19. rbesetup.sh
  20. README.md
  21. shell_utils.sh
  22. tapasHelp.sh
  23. 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.