| commit | 39cd33701c9278db0e7e481a090605f428d5b12d | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Fri Nov 22 16:12:31 2024 -0800 |
| committer | Cole Faust <colefaust@google.com> | Mon Nov 25 14:48:52 2024 -0800 |
| tree | 97627fa1d91cb5f749fa7e0521652388b82127e6 | |
| parent | 00338e915e32eb2dec0eeb7ee6771319944269ae [diff] |
Salt init_boot and vendor_boot using the build number If you don't provide a salt, avbtool uses random bytes as the salt. The randomness is bad for build caching and being able to diff partitions to ensure code changes aren't breaking anything. It's not exactly clear if the salt is necessary at all or not, but as an intermediate step, salt the images using the build number instead of purely random bytes. I've only done the init_boot and vendor_boot partitions in this cl, but I plan to expand it to all the other partitions. There are other diffs besides the avb hash in those partitions right now though so it's harder to test. Bug: 380508890 Test: m soong_generated_init_boot_filesystem_test Change-Id: I56289509497a2f0d500ffbbd677517fa0f748340
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.