| commit | bab814f33022363ce34987a73992d2870d3e6124 | [log] [tgz] |
|---|---|---|
| author | Dan Albert <danalbert@google.com> | Wed Aug 26 15:34:53 2020 -0700 |
| committer | Dan Albert <danalbert@google.com> | Wed Sep 16 16:20:59 2020 -0700 |
| tree | e8a5dd1294e8b986f14539a94a6c8f1785593bb8 | |
| parent | 53a80be100ae92721320b81a90eefebfef02b660 [diff] |
Add a showcommands function to envsetup. This is similar to the old `m showcommands`, but operates on specific output paths instead and does not require a build aside from the initial invocation of soong to generate the ninja files. The `--regenerate` option is accepted that causes the ninja file to be regenerated first, but this is not the default because it is slow. Just note that without this flag results may be stale. It unfortunately doesn't work for everything in out. For example, `$OUT/system/lib/libc.so` won't work because it is a symlink that isn't in the build graph, but `$OUT/system/lib/bootstrap/libc.so` works. Test: showcommands out/target/product/walleye/system/lib/libz.so Bug: None Change-Id: I4cfded3db994044870fc71ae4bcf9a69224b1e15
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.