| commit | 92afd7d1e75dd06f27119353d465fed72f0b0592 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Wed May 02 00:15:41 2018 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed May 02 00:15:41 2018 -0700 |
| tree | 0085a661943a6cdf89621b9e3eb64ba66a6896c3 | |
| parent | 88727e2422d2e1689f76398abd605b09373b7973 [diff] |
Accept TARGET_DEVICE_DIR preserved from previous product load During a build, we load product configuration three different times -- to dump some initial variables, when parsing the CleanSpec.mk files, and again when we parse the Android.mk files. The BoardConfig.mk find commands use -path, which isn't supported by the Kati find optimizer, so we end up spending ~125ms in each of the above cases (on my machine, internal master -- aosp is closer to 30ms). Instead, do the search during the initial dumping of variables, and pass in TARGET_DEVICE_DIR into the later runs, using that to load the BoardConfig.mk file. Bug: 78020936 Test: out/build-taimen.ninja is identical Test: out/soong.log shows that we're not running these finds again Change-Id: I6f186e1879aa362528b48b8a00be3f7a9f88bfc5
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.