Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / 8f559e099d3263de0ab265a301c7d52f964e7055
commit8f559e099d3263de0ab265a301c7d52f964e7055[log] [tgz]
authorRemi NGUYEN VAN <reminv@google.com>Thu May 12 13:17:02 2022 +0900
committerRemi NGUYEN VAN <reminv@google.com>Thu May 12 13:20:51 2022 +0900
treec4161eead4c85d53d317338358124be0204d7194
parent5e3cd45b5c3141e94d2f9da9152aad76974df31a [diff]
Use non-next NetworkStack

NetworkStack now builds against stable T APIs, so T can use
the stable binaries instead of the "next" versions.

Since it has just been bumped, NetworkStack is equivalent to
NetworkStackNext at this point, so this is a no-op.

This change should not go into development branches using unstable SDKs
(including aosp/master downstreams), as per the merged-in.

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