| commit | 83eeebb4df97ca5f0dbae62ce1664dc612215d8e | [log] [tgz] |
|---|---|---|
| author | Jingwen Chen <jingwen@google.com> | Wed Oct 05 02:27:07 2022 +0000 |
| committer | Jingwen Chen <jingwen@google.com> | Wed Oct 05 04:11:22 2022 +0000 |
| tree | bdc69a09b80ee519c6c2475e5205e26bf8eb2e39 | |
| parent | 694cb51d7ebd614dc0790ff0e4c1ce17590a6759 [diff] |
envsetup: add bmod to get Bazel label of a Soong module. This benefits interactive workflows of folks who are used to typing just module names on the command line, and lowers the cognitive load to find the package name, and can be used to check if a module is converted. Can be used as : $ bmod libaapt2 //frameworks/base/tools/aapt2:libaapt2 $ b build $(bmod aapt2) If the mod is not in the bp2build metrics file, it returns: $ bmod nonexistent nonexistent is not converted to Bazel. Test: build/make/core/tests/b_tests.sh Change-Id: I245665a393621a47598e6743c0fedcd87ac33631
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.