| commit | 3d38b6d9c803f6b04d71f620a0c1417a1c7973cb | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Fri Oct 28 22:21:42 2022 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Fri Oct 28 22:45:08 2022 +0000 |
| tree | 7a65d65b614d424313594050a4426514ec4bbebe | |
| parent | 03b846ff370e9d4b3e7adf34c363837425f4611d [diff] |
Create custom diff tool to compare stub contents Context: - Create a tool to analyze loose equivalence of the stubs in two directories - The tool can analyze strict equivalence of the directories of the stubs in two directories - Analyze text to compare loose equivalence of the stub contents; Add a functionality to pass `skip_words` as arguments, which are optional list of words used to signal the tool which words are not considered diff - The tool can be locally used to compare stub contents, and does not contribute to build process Test: m Change-Id: I74563a9a24ecdde939be2ce37b9096a9aeb4920a
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.