| commit | 89a470255549852cd1f86391e6279b73320e4727 | [log] [tgz] |
|---|---|---|
| author | Sam Delmerico <delmerico@google.com> | Tue Apr 05 13:44:18 2022 +0000 |
| committer | Sam Delmerico <delmerico@google.com> | Tue Apr 05 13:47:32 2022 +0000 |
| tree | 2c28b8c03b2741795b688b6739e01648ddc07a80 | |
| parent | 4a723d0ecf16e075bc5ff79d456f3d78c2149ef1 [diff] |
prevent unintended m bp2build "" when running b cl/2045666 allowed the --skip-soong-tests flag to pass through invocations of the `b` command to soong_ui. But when the flag was missing, an extra `""` argument was passed instead which caused soong_ui to invoke a build of the droid target. Test: m clean && b build '...' # verify Soong does not run a build Change-Id: I7b99437d225786eb1698a88d0c755ce897550e70
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.