| commit | ac48f41ba561233fe0372da939051f27d3ceb422 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed Mar 28 22:36:00 2018 -0700 |
| committer | Colin Cross <ccross@android.com> | Tue Apr 10 16:27:53 2018 -0700 |
| tree | 03c98f557a80fbbd938cab3b2f6baf1c1c292e94 | |
| parent | f05573eb91401f19d2dae579ce6220d4b5680212 [diff] |
Don't depend on R.txt) There is an extra ) in the implicit output path for R.txt, which causes the rule to rerun every time because of a missing output file. There is already an implicit output for R.txt on line 180 (which is why the incorrect path didn't cause an immediate "No rule to generate R.txt" error), so just remove the incorrect one. Bug: 77244156 Test: m checkbuild && m checkbuild Change-Id: Id960ee211b89a9a5f5104cdcac23bc3124742145
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.