| commit | 3438181b4b57617e6c45ba76689f7c530dc556bd | [log] [tgz] |
|---|---|---|
| author | Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> | Thu Mar 13 15:52:23 2025 -0700 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Thu Mar 13 15:52:23 2025 -0700 |
| tree | 8b94beaa163fa37b6de3ab9cde47e9205c58af98 | |
| parent | b8503dbcc90835e1ba44b3d705ca427b338ffe06 [diff] | |
| parent | 5db2b8fa45a8ba9e90f76f583bc46ffdcf6c3c57 [diff] |
Merge changes Ibf4f6584,Icd55ed1b,Idecd2f00,I00a62769,I80c56064 into main * changes: Replace test suites symbols.zip name patterns Remove redundant entries from symbols.zip Create symbols.zip per test suite Generate symbols mapping files for jni libs Modify the params of copy-unstripped-elf-file-with-mapping
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.