| commit | 4eb1aa94cc916c4aef4d68cf4f2e6470b1d5b1f5 | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Wed Jun 08 21:09:30 2022 +0000 |
| committer | Spandan Das <spandandas@google.com> | Wed Jun 08 21:14:52 2022 +0000 |
| tree | f749da82d593b5922ecabd296fe19d51a8be9e54 | |
| parent | ac7eeb78ef43c6a78f8733868d670a99d568f377 [diff] |
Fix broken test_lunch.py The orchestrator path inside the test workspace (test/configs) is build/make, which is different from the current path in multitree (build/build/make). This was causing `python test_lunch.py` to fail Rather than restructing the test workspace to build/build/make now (and build/ later when the orchestrator is in its own project), create a Context object which can be mocked. Test: python test_lunch.py Change-Id: Ibd89c3ff0204ebad320c90a05bab4c0f8c86b3a0
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.