commit | a3c088ce1d6030c36d340efb974ba3f83cc5f005 | [log] [tgz] |
---|---|---|
author | Wei Li <weiwli@google.com> | Mon Nov 04 09:31:14 2024 -0800 |
committer | Wei Li <weiwli@google.com> | Tue Nov 05 22:16:03 2024 +0000 |
tree | d255a620b8bda93c016f743e1254503ab475a807 | |
parent | 490590b722ec74477cade0971b57684738126123 [diff] |
Convert build/make/tools/fs_config/Android.mk to Android.bp And export soong config variables of paths of *_dlkm partitions and whether they are built for a product. Bug: 377304441 Test: lunch aosp_cf_x86_64_phone-trunk_staging-eng && m, check fs_config_dirs and fs_config_files exist in etc/ in each partitions Change-Id: I45decac561d5aadfb9e59dfc4157fd3699e65c9b
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.