Rename mainline_system to generic_system in mk files to avoid confusion with mainline module. First, move mainline_system(.*).mk to generic_system(.*).mk and make previous mainline_system(.*).mk to just inherit generic_system(.*).mk to make alias except mainline_system.mk. is just symlink to generic_system.mk. These aliasing file will be kept remain during migration for preventing build breakage and making changes possible during migration. Bug: 160649682 Test: lunch generic_system_arm64 && m nothing Test: lunch generic_system_x86 && m nothing Test: lunch generic_system_x86_64 && m nothing Test: lunch generic_system_x86_arm && m nothing Test: lunch mainline_system_arm64 && m nothing Test: lunch mainline_system_x86 && m nothing Test: lunch mainline_system_x86_64 && m nothing Test: lunch mainline_system_x86_arm && m nothing Change-Id: I3609ec2d91b0f08859a36cac75c25876b1db6d6a
15fbad3dfa
am: d4aef1614a
am: 249430d062
am: e6d1bf14e7
am: 518a3a20b5
76279b102f
am: 136824c6e9
am: d5f7720189
am: 4ba5a65bdd
am: 8abf64c13f
99e317ce2d
am: 3af5f639bb
am: 24a87ba928
am: bc9322142c
5d0a024d7b
am: 479c9c549b
Android Make Build System
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.