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:
@@ -563,11 +563,11 @@ func (binary *binaryDecorator) verifyHostBionicLinker(ctx ModuleContext, in, lin
|
||||
}
|
||||
|
||||
type ccBinaryBazelHandler struct {
|
||||
BazelHandler
|
||||
|
||||
module *Module
|
||||
}
|
||||
|
||||
var _ BazelHandler = (*ccBinaryBazelHandler)(nil)
|
||||
|
||||
func (handler *ccBinaryBazelHandler) QueueBazelCall(ctx android.BaseModuleContext, label string) {
|
||||
bazelCtx := ctx.Config().BazelContext
|
||||
bazelCtx.QueueBazelRequest(label, cquery.GetOutputFiles, android.GetConfigKey(ctx))
|
||||
|
Reference in New Issue
Block a user