| commit | 988bcf6dc2594dfe0178bbbfb4de0871495fdc1b | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed Aug 21 10:45:27 2024 -0700 |
| committer | Colin Cross <ccross@android.com> | Wed Aug 21 10:53:35 2024 -0700 |
| tree | 4f70e1ed12479218fc3f32632f6dac2de99b2477 | |
| parent | 651fa7511214c4417195e5a3a523e96f89211a1d [diff] |
Move checkbuild targets of Soong modules into Soong Let Soong specify the files that will be built by checkbuild for each Soong module. This will give better control over which files get built, allowing checkbuild to skip the jar combining step when transitive classpath jars are enabled. Bug: 308016794 Test: m checkbuild Change-Id: Ic5140819381d58f4d00f23a7a12447950c4cf268
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.