Spandan Das 6d4d9da47f Select stub/impl per apex variant ... Create a select statement for every api_domain a library could be included in. The stub/impl selection heuristics per apex domain are 1. If dep has stubs and the api domain appears in dep's apex_available, use impl 2. If dep has stubs and the api domain does not appear in dep's apex_available, use stubs (Category 3: If dep does not have stubs and the apex does not appear in dep's apex_available, then a separate apex_available validation in Bazel will emit an error). Platform variants have been special-cased for now to use equality of apex_available for stub/impl selection Test: go test ./bp2build Bug: 272378496 Change-Id: Ibd29efd763c8863c7e6d2a9af0da30bbde07175d		2023-05-08 21:11:46 +00:00
..
cquery	Revert "Revert "mixed builds correctly reference stubs libs""	2023-04-25 00:25:20 +00:00
Android.bp	Add a persistent bazel server between builds	2023-03-01 23:30:19 -05:00
aquery.go	Handle aquery build statements in a goroutine	2023-02-15 11:29:49 -05:00
aquery_test.go	Handle aquery build statements in a goroutine	2023-02-15 11:29:49 -05:00
bazel_proxy.go	Refactor and cleanup of bazel handler	2023-04-25 15:53:58 +00:00
configurability.go	Select stub/impl per apex variant	2023-05-08 21:11:46 +00:00
constants.go	refactor Bazel variable export	2022-04-06 14:48:32 +00:00
properties.go	Broaden the granularity of config_setting from apex_name to api_domain	2023-05-04 22:06:47 +00:00
properties_test.go	Correct global excludes not always being excluded	2023-01-26 11:16:39 -05:00
testing.go	add unit test for bp2build allowlist	2022-04-14 13:31:09 +00:00