Don't use arch-specific modules when we want a single module
This breaks when two host OSes are enabled for example. Bug: 31559095 Test: enable host bionic as a second Host OS, attempt a build Test: treehugger Change-Id: If52f77d7d3b0755d768028cbddda320303a69e65
This commit is contained in:
parent
0ef639bb59
commit
4f644da0ad
|
@ -278,11 +278,7 @@ func versionedNdkHeadersFactory() android.Module {
|
|||
|
||||
module.AddProperties(&module.properties)
|
||||
|
||||
// Host module rather than device module because device module install steps
|
||||
// do not get run when embedded in make. We're not any of the existing
|
||||
// module types that can be exposed via the Android.mk exporter, so just use
|
||||
// a host module.
|
||||
android.InitAndroidArchModule(module, android.HostSupportedNoCross, android.MultilibFirst)
|
||||
android.InitAndroidModule(module)
|
||||
|
||||
return module
|
||||
}
|
||||
|
@ -362,11 +358,7 @@ func preprocessedNdkHeadersFactory() android.Module {
|
|||
|
||||
module.AddProperties(&module.properties)
|
||||
|
||||
// Host module rather than device module because device module install steps
|
||||
// do not get run when embedded in make. We're not any of the existing
|
||||
// module types that can be exposed via the Android.mk exporter, so just use
|
||||
// a host module.
|
||||
android.InitAndroidArchModule(module, android.HostSupportedNoCross, android.MultilibFirst)
|
||||
android.InitAndroidModule(module)
|
||||
|
||||
return module
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue