Handle already existing targets of different name

In other words, if, in bp2build, module "foo" would generate "foo",
and "foo_two", and "foo_two" already exists in a build file,
bp2build should label "foo" as being unconvertible.

Fixes: 301321658
Fixes: 301312582
Bug: 285631638
Test: Unit tests
Test: Verified that `m bp2build` results in bit-for-bit identical
contents for out/soong/bp2build before and after this change.

Change-Id: Icbbdd69fce83579ec9b172d04b2bf1f294698f70
This commit is contained in:
Chris Parsons
2023-09-21 20:36:35 +00:00
parent 92c59496e0
commit 0c4de1f234
9 changed files with 86 additions and 79 deletions

View File

@@ -112,7 +112,7 @@ filegroup {
}
cc_binary { name: "cc_binary_1"}
sh_binary { name: "sh_binary_2"}
sh_binary { name: "sh_binary_2", src: "foo.sh"}
apex {
name: "com.android.apogee",
@@ -609,7 +609,7 @@ filegroup {
}
cc_binary { name: "cc_binary_1" }
sh_binary { name: "sh_binary_2" }
sh_binary { name: "sh_binary_2", src: "foo.sh"}
apex {
name: "com.android.apogee",
@@ -736,7 +736,7 @@ filegroup {
}
cc_binary { name: "cc_binary_1"}
sh_binary { name: "sh_binary_2"}
sh_binary { name: "sh_binary_2", src: "foo.sh"}
apex_test {
name: "com.android.apogee",