| commit | 3357cf912e6c4baafd026dae699d9175ddea400c | [log] [tgz] |
|---|---|---|
| author | Kousik Kumar <kousikk@google.com> | Fri Mar 31 09:57:01 2023 +0000 |
| committer | Kousik Kumar <kousikk@google.com> | Fri Mar 31 09:57:01 2023 +0000 |
| tree | cdb0197aebe106a59e46cab252d6695635dc5ecc | |
| parent | 09df4c65622fba042d5a31cd12a70dd47d785763 [diff] |
Make sort as part of the inner command It turns out, in Cog workspaces, the order of files returned by "find" command is inherently non-deterministic (they use an absl::HashMap which intentionally tries to NOT guarantee sort order). This results in varying order for the inner variable, which actually causes invalidation and regeneration of the build graph (I'm guessing when "y" changes in $(sort $(y)), it causes an invalidation in Make). Hence made the sort a part of the inner command itself. Tested: Ran the build with Cog and ensured graph wasn't regenerated across reruns. Bug: b/276397558 Change-Id: Ie772572048785793067f74c08ac3994ef6cbaa43
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.