Stop relying on target.kind in mixed builds.
target.kind was a field that existed for only a few months, and have been removed from Bazel. This is needed to update to a newer Bazel version. Also, this reverts filegroups to be queried for a specific arch again, but leaving file targets in the common arch (which is correct, anyway). Fixes: b/199363072 Test: mixed_libc Test: presubmits Change-Id: I3b8e5c43a39516d977d327a44a75750b2f251be3
This commit is contained in:
@@ -587,13 +587,11 @@ def %s(target):
|
||||
%s
|
||||
|
||||
def get_arch(target):
|
||||
# TODO(b/199363072): filegroups and file targets aren't associated with any
|
||||
# specific platform architecture in mixed builds. This is consistent with how
|
||||
# Soong treats filegroups, but it may not be the case with manually-written
|
||||
# filegroup BUILD targets.
|
||||
if target.kind in ["filegroup", ""]:
|
||||
return "common"
|
||||
buildoptions = build_options(target)
|
||||
if buildoptions == None:
|
||||
# File targets do not have buildoptions. File targets aren't associated with
|
||||
# any specific platform architecture in mixed builds.
|
||||
return "common"
|
||||
platforms = build_options(target)["//command_line_option:platforms"]
|
||||
if len(platforms) != 1:
|
||||
# An individual configured target should have only one platform architecture.
|
||||
|
Reference in New Issue
Block a user