| commit | df1b7d1d817d07772073a8ee35dc1d83b6872047 | [log] [tgz] |
|---|---|---|
| author | Marybeth Fair <marybethfair@google.com> | Fri Aug 30 15:37:27 2024 +0000 |
| committer | Marybeth Fair <marybethfair@google.com> | Tue Sep 03 16:24:51 2024 -0400 |
| tree | 544206af8de5fdaa5672c0aa8803aa4a4408115d | |
| parent | 0ad443b80cda57beae30f17d77c0b7759c2e3e4a [diff] |
Add a function to fingerprint flag/offset info. Uses SipHasher implementation added to the project. Ideally the output would remain consistent between builds (though the worst case of an updated algorithm would be a string lookup for cross-container reads only). Sort the flags first so everything is always added to the hasher in the same order - note this code is only run at build time, not runtime. Next step is to write this fingerprint into the package.map file and introduce a flag to guard this change. Bug: 316357686 Test: atest aconfig.test Change-Id: Ie5f34541d982dfa120ffb05fc0790603689d47c0
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.