| commit | aacf2376a5fd5fc9923da22db31a5e3aa6ce4f70 | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Wed May 11 21:46:29 2022 +0000 |
| committer | Spandan Das <spandandas@google.com> | Thu May 12 17:47:29 2022 +0000 |
| tree | c1dd80d20233c56a5ae4d87f301a79a39a258d09 | |
| parent | a09c684e27f748b449f4fe0a5c0bf3527531fc8a [diff] |
Lightweight ninja writer in Python Summary: - Create python classes for ninja vocbulary in `ninja_syntax.py`. These classes will be serialized to a ninja file - Create a Writer class in `ninja_writer.py`. The current API supports adding variables,rules,build actions, etc. This can be extended in the future (See `test_ninja_writer.py` for examples) Future Work: - Update the `Subninja` class once chDir is supported (aosp/2064612) - Support a width parameter that will be used to wrap long lines of text. This will improve readability of the generated files Expected Use Case: Multi-tree build orchestrator Test: python ./test_ninja_syntax.py Test: python ./test_ninja_writer.py Change-Id: I90c7ee69ddeb7c20c3fd4fca5a911dddbf2253bd
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.