Spandan Das 4242f10462 Create config_setting per apex_name ... These are created by bp2build in /build/bazel/rules/apex. Eventually these config_settings should likely be colocated with the source apex definition. Another alternative was to make Bazel's apex a macro that generates a config_setting. I did not pursue this further for now since it requires the apex_available of every allowlisted cc_library to also be allowlisted. This might not always be true (e.g. com.android.runtime) Test: go test ./bp2build Change-Id: Ibbb14b0d9c1491b3c79b7634a18d9d35b03922c1		2023-04-28 20:37:35 +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	Create config_setting per apex_name	2023-04-28 20:37:35 +00:00
constants.go	refactor Bazel variable export	2022-04-06 14:48:32 +00:00
properties.go	Add a function to create config_setting(s)	2023-04-28 19:43:43 +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