| commit | 589e3bc83c071cddfa72917e9ac3b213d3fb5dfc | [log] [tgz] |
|---|---|---|
| author | Nelson Li <nelsonli@google.com> | Tue Mar 05 02:55:42 2024 +0000 |
| committer | Nelson Li <nelsonli@google.com> | Tue Mar 05 03:51:49 2024 +0000 |
| tree | 1074cdba09bb285e56ba0717c9be0a85722fe8ff | |
| parent | 61856ca3ed682509eceb5ca75d2dc24a1e5264f6 [diff] |
Move frameworks/base/Android.mk to build/tasks 1. Move the work of `declare-1p-copy-files` to `meta-lic.mk`. 2. Remove `$(LOCAL_PATH)/pathmap.mk` because the variables defined in it are no longer used. 3. The variable `ONE_SHOT_MAKEFILE` is deprecated and can be removed directly. 4. Move the main work of generating the targets `docs`, `offline-sdk-docs`, and `framework-doc-stubs` to `framework_library.mk`. Because Soong cannot specify the output to paths such as `$(OUT_DOCS)/` and `framework-doc-stubs-metadata_intermediates/`. 5. `ANDROID_BUILD_EMBEDDED` can theoretically be removed because the `.mk` files that use this variable are not currently in use, but since it involves many other files that are unrelated to this task, the work of removing this variable will be moved to other changes. Bug: 322732227 Test: m docs offline-sdk-docs framework-doc-stubs Change-Id: Ie51dbf88c78861fc60c6ba9c40542455e4cd4f55
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.