commit | 685029d3f3df7928027f6cd758c38256d2bcce16 | [log] [tgz] |
---|---|---|
author | Joe Onorato <joeo@google.com> | Thu Mar 20 14:40:20 2025 -0700 |
committer | Joe Onorato <joeo@google.com> | Thu Mar 20 14:42:53 2025 -0700 |
tree | 4556bf3cd870521bda22f599c2c4e7d082ae60d0 | |
parent | 8445b1703a24d34a2c6fc789f47cf81ceda3aaea [diff] |
Add benchmark for full analysis. Instead of touching an Android.bp file, delete the ninja files. The other 'android_bp' benchmark adds a comment to the ninja file, which hits the opimization that doesn't make kati rerun. Bug: 399467514 Test: build/make/tools/perf/benchmarks --benchmark full_analysis Change-Id: I47d852add5d714d7edea7ba5e7dbbeac75b07a74
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.