| commit | 400673cf1e1efb9f7f9a83d499a32546a6e1dcc9 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Tue Apr 10 16:16:33 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Tue Apr 10 18:53:30 2018 +0100 |
| tree | c8f1276013fef09ca12213c759c8b1781c2a7437 | |
| parent | f05573eb91401f19d2dae579ce6220d4b5680212 [diff] |
Consolidate the logic for the sdk prebuilt module names. I'm making some changes to it, and found the names are scattered in various places. Make a macro and re-use the logic instead. Bug: 77525052 Test: make droid Change-Id: I0f2da80b8b4d427353509b27ec720d024eee7a6e
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.