| commit | 62054a43fa0c5a7f708b636806ccc09636b985f5 | [log] [tgz] |
|---|---|---|
| author | Steven Moreland <smoreland@google.com> | Thu Dec 06 10:11:40 2018 -0800 |
| committer | Steven Moreland <smoreland@google.com> | Thu Dec 06 18:28:50 2018 -0800 |
| tree | c6d8ce0df598f948c8c35606b1c4b3ca444953e6 | |
| parent | 5fbe6abfb71d4e14c8162a4049b3c0f6a67666ff [diff] |
Add functions to jump to specific modules. Usage: ...aosp/$ gomod libbase ...aosp/system/core/base$ Using in alias: alias g=gomod complete -F _complete-android-module-names g ...aosp/$ g libbase ...aosp/system/core/base$ Nothing in Android keeps an up to date index of all Android modules and their locations between builds. However, there is a target 'module-info.json' which is used to contain some of that information. This module can be updated using the command 'refreshmod' added here, but it will also be updated during a normal Android build. This also adds auto-complete for m. Bug: N/A Test: manual Change-Id: I06b0b87c308b9fe2798dbc29225906cc30fe59fe
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.