Don't enable ADB by default on userdebug builds

includes the following commit:

commit c2bb9607e09d899d2ea0a0f87ff43dc2b66068f1
Author: Scott Mertz <scott@cyngn.com>
Date:   Thu Feb 26 10:51:44 2015 -0800

    Enable ADB by default when ro.adb.secure is not 1

    * Property ro.build.type is not part of the default.prop we can't
      use this to decide how to apply adb by default within this function

    Change-Id: Ib3eb24c655353966d64c7148d7530244b628ce94

Issue: FP2A10-180
Change-Id: I33ae5c6f2787017a62e679aa0c28d4b909d45935
1 file changed
tree: 3c13859b00e2041912af3a0e5e6b53353f1506d3
  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.