| commit | 2bfc570d8f194230896acb1df335b079190f4be2 | [log] [tgz] |
|---|---|---|
| author | Sasha Smundak <asmundak@google.com> | Wed Jun 22 16:24:47 2022 -0700 |
| committer | Sasha Smundak <asmundak@google.com> | Fri Jun 24 09:57:45 2022 -0700 |
| tree | 1862ae5000e3c1316a59e36e89e4d9492a1065ea | |
| parent | dc08c346fbfec8238d79ae2a42bf680550a7bcdf [diff] |
Copy symlink farm creation tool from Bazel. SymlinkTree is one of the action types Blaze returns in response to `aquery` (action query). build-runfiles is a tool copied from Bazel to implement this action (see src/main/tools/build-runfiles.cc in the Bazel Git repo). It creates a symlink farm (i.e., a directory hiearchy consisting of symlinks) from a given manifest. Mixed builds need this tool the mixed builds (in particular, every Python applicaion has a runtime symlink farm). Bug: 232085015 Test: m USE_BAZEL_ANALYSIS=1 com.android.adbd Change-Id: I9cfcb33cb7d0f63bd36ffd2b4101f53cfc6a42fc
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.