| commit | 13cb165b91da3881081f9fead865c1e262943269 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Thu Dec 26 16:27:36 2019 -0800 |
| committer | Dan Willemsen <dwillemsen@google.com> | Thu Dec 26 16:52:34 2019 -0800 |
| tree | c6d10647d8d86213684bab424c8d414e5f0775b0 | |
| parent | 7c18a371471123ce678f49e446edbf748eb80380 [diff] |
Stop removing valid copy headers My change to clean up obsolete copy headers would remove valid ones if thhe LOCAL_COPY_HEADERS_TO path wasn't cleaned. I'm seeing this most with values that just end in '/', so we end up with a '//' in the path, which isn't textually equivalent, and we remove it. Test: No longer seeing constant removals on internal products Test: Set LOCAL_COPY_HEADERS_TO := .. Test: Set LOCAL_COPY_HEADERS_TO := ../foo Test: Set LOCAL_COPY_HEADERS_TO := /foo Change-Id: Idbeeb207a2bb2a8da766473dbded877cec7c9cc1
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.