From eb3358cfa7c54c7922e7f9459256ade0923dd57a Mon Sep 17 00:00:00 2001
From: Anton Hansson <hansson@google.com>
Date: Thu, 5 Jul 2018 15:57:56 +0100
Subject: [PATCH] Add documentation for module resolution.

I found this in the CL description of
I5fda1a77f58814097b10b5ad2743ee25adfaecc4, and modified it slightly.

Bug: 111154853
Test: No
Change-Id: I984ac1a9521357af6b54340939dcde36988fc634
---
 core/main.mk | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/core/main.mk b/core/main.mk
index bc99284228..0d2cc348fa 100644
--- a/core/main.mk
+++ b/core/main.mk
@@ -895,6 +895,14 @@ endef
 # The base list of modules to build for this product is specified
 # by the appropriate product definition file, which was included
 # by product_config.mk.
+# Name resolution for PRODUCT_PACKAGES:
+#   foo:32 resolves to foo_32;
+#   foo:64 resolves to foo;
+#   foo resolves to both foo and foo_32 (if foo_32 is defined).
+#
+# Name resolution for LOCAL_REQUIRED_MODULES:
+#   If a module is built for 2nd arch, its required module resolves to
+#   32-bit variant, if it exits. See the select-bitness-of-required-modules definition.
 # $(1): product makefile
 define product-installed-files
   $(eval _pif_modules := $(PRODUCTS.$(strip $(1)).PRODUCT_PACKAGES)) \