commit | 9d924f67d3a16c45d439e1c8d284e441e8041406 | [log] [tgz] |
---|---|---|
author | Tom Cherry <tomcherry@google.com> | Wed Feb 13 14:02:30 2019 -0800 |
committer | Tom Cherry <tomcherry@google.com> | Fri Feb 15 09:44:09 2019 -0800 |
tree | 6ad81259e55bc8f57726d06b1aa83872b5ba076d | |
parent | 1a9f8356fd2a895262d4de2ab32a03e4474555f9 [diff] |
Use fs_config_generator.py to generate fs_config_files/dirs directly We want to remove target specific host tools and since fs_config_generate is compiled with a target specific header file, we instead remove fs_config_generate entirely and allow python to build the fs_config_files/dirs files directly from config.fs files and parsed C headers. Test: associated unit tests and new end to end test Test: aosp_sailfish, aosp_crosshatch build produces valid fs_config files Test: aosp_cf_x86_phone build correctly produces empty fs_config files Change-Id: Idbc63ff56c0979e1e4c17721371de9d9d02dc8ff
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.