| commit | c35895676cf558d8e16a38d0dc931f7b348717c6 | [log] [tgz] |
|---|---|---|
| author | Joe Onorato <joeo@google.com> | Fri May 13 12:10:23 2022 -0700 |
| committer | Joe Onorato <joeo@google.com> | Thu May 26 15:11:23 2022 -0700 |
| tree | de4a18cad05d11c0d06c28c4f590f29e43428dff | |
| parent | 4117e78575fafb8a30d0f1ca5c19c130ed744c3a [diff] |
Orchestrator can build end to end. This reduces the scope of the demo to just building and installing a single .so, but it makes the demo actually build that single .so. Next up, writing some unit tests and fleshing out functionality. Test: see the README Change-Id: I560904b786fbf69d3a83dbb08d496dba5a3192ca
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.