| commit | b82ef911f9cd3e8da245dc438f931a5f84122a1b | [log] [tgz] |
|---|---|---|
| author | Elliott Hughes <enh@google.com> | Tue Jun 25 09:07:41 2019 -0700 |
| committer | Elliott Hughes <enh@google.com> | Tue Jun 25 09:07:41 2019 -0700 |
| tree | 5056bb14783d6588ee72b3b5015cd8c3b61a63b6 | |
| parent | 3771cff8343c9031ea8c6e01c33efa9e60e0acab [diff] |
Don't use tar's -p with -rf, where it makes no sense. -p only applies to tar invocations that cause extraction, but -rf is just appending to a tar file. toybox tar doesn't have -p, and it doesn't seem worth implementing if this is our only "user". Test: treehugger Change-Id: I025c496b04cb57cb31ba81fd516fd40b158bc06b
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.