commit | 3fe369c271888fef9b2d21a145b241aa36314bfd | [log] [tgz] |
---|---|---|
author | Bob Badour <bbadour@google.com> | Sun Dec 18 14:15:02 2022 -0800 |
committer | Bob Badour <bbadour@google.com> | Wed Jan 04 00:01:49 2023 +0000 |
tree | 2a6d8b6cf64136da29e7ae171731061a6d9435e1 | |
parent | 42b02efd0568dccd4ccad8c1473b35521c0f3bec [diff] |
An ActionSet doesn't need to walk the graph. Resolutions map back to the root, but actions do not. An iteration works just fine. Simplify TargetNodeSet so that it is directly iterable. Bug: 261787132 Test: m droid dist compliance_dumpgraph compliance_dumpresolutions \ compliance_sbom compliance_listshare compliance_rtrace \ compliance_checkshare xmlnotice textnotice htmlnotice \ compliancenotice_shippedlibs compliancenotice_bom Test: m compliance_checkshare cts && \ out/host/linux-x86/bin/compliance_checkshare out/host/linux-x86/gen/META/lic_intermediates/out/host/linux-x86/cts/android-cts.zip.meta_lic Change-Id: Ic5a2d809b5a9a47b5d85f61e3a4a790dbe8f5fd2
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.