Do not add .bp files to the .d file of bp2build.
This is okay because Blueprint already adds the module files to the .d file of its output, so until now, they were duplicated. Test: presubmits Change-Id: I1bb75c5124aadd1703f3d150948dd7540ba772be
This commit is contained in:
@@ -616,21 +616,11 @@ func runBp2Build(configuration android.Config, extraNinjaDeps []string) {
|
||||
bp2buildCtx.SetAllowMissingDependencies(configuration.AllowMissingDependencies())
|
||||
bp2buildCtx.SetNameInterface(newNameResolver(configuration))
|
||||
bp2buildCtx.RegisterForBazelConversion()
|
||||
bp2buildCtx.SetModuleListFile(cmdlineArgs.ModuleListFile)
|
||||
|
||||
var ninjaDeps []string
|
||||
ninjaDeps = append(ninjaDeps, extraNinjaDeps...)
|
||||
|
||||
// The bp2build process is a purely functional process that only depends on
|
||||
// Android.bp files. It must not depend on the values of per-build product
|
||||
// configurations or variables, since those will generate different BUILD
|
||||
// files based on how the user has configured their tree.
|
||||
bp2buildCtx.SetModuleListFile(cmdlineArgs.ModuleListFile)
|
||||
if modulePaths, err := bp2buildCtx.ListModulePaths("."); err != nil {
|
||||
panic(err)
|
||||
} else {
|
||||
ninjaDeps = append(ninjaDeps, modulePaths...)
|
||||
}
|
||||
|
||||
// Run the loading and analysis pipeline to prepare the graph of regular
|
||||
// Modules parsed from Android.bp files, and the BazelTargetModules mapped
|
||||
// from the regular Modules.
|
||||
|
Reference in New Issue
Block a user