commit | 7c01d47c9a737095125fa0b5b0e6bc3bfceee3b9 | [log] [tgz] |
---|---|---|
author | Joe Onorato <joeo@google.com> | Tue Jan 19 22:14:23 2021 -0800 |
committer | Joe Onorato <joeo@google.com> | Wed Feb 17 10:02:41 2021 -0800 |
tree | 3c00ae80daf6d830d4e8ed1ce42c2426258ff6c1 | |
parent | 43d4040f6f3f65b13673f03639b65f6c37c3ea8e [diff] |
Add a CSV parser to parse the output from kati. (Yet another class that would be great for android to have in a host tools library) Test: m product-config-test && java -jar out/host/linux-x86/testcases/product-config-test/product-config-test.jar Change-Id: I7d74b2265393e4f340729ca5ba82d1ec92a20f85
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.