Allow creation of BazelTargets in a different directory
The current API restricts creation of targets to the directory of the
visited soong module. This CL proposes adding a `Dir` property in
`CommonAttributes` that can be used to create a bazel target in
a specific dir. The use case for this is to dynamically create
additional targets for proto_library that are adjacent to .proto files
(Bazel poses a strict requirement about proto_library being in the
same package as the .proto file, but Soong does not)
Usage is restricted to dirs that have an existing Android.bp file. There
are some places in bp2build where we use existence of Android.bp/BUILD
on filesystem to curate a compatible fully qualified path (e.g. headers).
If we use `CommonAttributes.Dir` to arbritraily create BUILD
files, then it might render those curated labels incompatible.
Test: go test ./bp2build
Change-Id: If9446700457eddfb389be9d9bde39087f67daa60
diff --git a/android/module.go b/android/module.go
index 4c781f6..5fecd83 100644
--- a/android/module.go
+++ b/android/module.go
@@ -1021,6 +1021,11 @@
Applicable_licenses bazel.LabelListAttribute
Testonly *bool
+
+ // Dir is neither a Soong nor Bazel target attribute
+ // If set, the bazel target will be created in this directory
+ // If unset, the bazel target will default to be created in the directory of the visited soong module
+ Dir *string
}
// constraintAttributes represents Bazel attributes pertaining to build constraints,