| commit | bd3821451ad20e81b773cad9eb249bcce8e84871 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed Aug 26 15:08:57 2020 -0700 |
| committer | Colin Cross <ccross@android.com> | Thu Aug 27 15:06:23 2020 -0700 |
| tree | 9f25c34a572862ee43360e64be082fe1d8fd9725 | |
| parent | 78439f466813bd93d2575e2c50aa2c81c85787ab [diff] |
Use rules to create partition compatibility symlinks Creating the symlinks between partitions (e.g /system/vendor to /vendor) inside the packaging rules requires duplicating the creation in the system.img rule as well as in the the target-files.zip rule, which can cause the target-files.zip rule to fail in soong_zip when the symlink is removed and recreated by the system.img rule. Now that our Ninja fork supports symlinks in the build graph, move the symlink creating to their own rules and add them to the list of files that the image creation and packaging rules depend on. Fixes: 161280160 Test: m nothing Test: treehugger Change-Id: I0f4d16b57b3052efb12a1f086506f1298c22ec84
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.