| commit | e16def0987dda45904cd712cb2c81765e8d4841a | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Fri Jan 06 16:19:26 2023 -0800 |
| committer | Cole Faust <colefaust@google.com> | Fri Jan 06 16:20:59 2023 -0800 |
| tree | fe995782b44ec40e53bb907793a92317dfe014df | |
| parent | 89a9f55d937d11cd4e8a09343825e616b3067d86 [diff] |
Remove duplicates from VendorVars maps Some products access the SOONG_CONFIG variables directly, instead of using soong_config_set. When they do that, they could end up with duplicate values in those variables, causing duplicate keys to be generated in a json map. Use $(sort) to dedup the map keys before writing them out. Bug: 249685973 Test: Presubmits Change-Id: If0c16377bdfbd3f836ebec9262bec7cf562f339c
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.