cc bazel handlers: use better interface checking

This is a far better approach for ensuring that bazel handlers implement
the BazelHandler interface, as it causes a compile error if they do not
implement the appropriate interface methods.

Test: Manually verified no change in ninja file
Change-Id: I63a4f8b57e3aedd4c0915c2fd2eb7029e9a993aa
This commit is contained in:
Chris Parsons
2022-05-20 10:54:17 -04:00
parent 489128b8ef
commit 6ce2cf9b69
5 changed files with 12 additions and 12 deletions

View File

@@ -407,12 +407,12 @@ type prebuiltObjectLinker struct {
}
type prebuiltStaticLibraryBazelHandler struct {
BazelHandler
module *Module
library *libraryDecorator
}
var _ BazelHandler = (*prebuiltStaticLibraryBazelHandler)(nil)
func (h *prebuiltStaticLibraryBazelHandler) QueueBazelCall(ctx android.BaseModuleContext, label string) {
bazelCtx := ctx.Config().BazelContext
bazelCtx.QueueBazelRequest(label, cquery.GetCcInfo, android.GetConfigKey(ctx))
@@ -458,12 +458,12 @@ func (h *prebuiltStaticLibraryBazelHandler) ProcessBazelQueryResponse(ctx androi
}
type prebuiltSharedLibraryBazelHandler struct {
BazelHandler
module *Module
library *libraryDecorator
}
var _ BazelHandler = (*prebuiltSharedLibraryBazelHandler)(nil)
func (h *prebuiltSharedLibraryBazelHandler) QueueBazelCall(ctx android.BaseModuleContext, label string) {
bazelCtx := ctx.Config().BazelContext
bazelCtx.QueueBazelRequest(label, cquery.GetCcInfo, android.GetConfigKey(ctx))