Delete SyspropMutator
This CL and its associated CLs point cc modules that rely on sysprop_library modules to the auto-generated cc_library module, and then remove the code in Soong which maps the sysprop_library target to the generated target. This is being done because Bazel will not be supporting the existing behavior in Soong. Bug: 226199990 Test: m Change-Id: I117c5a4a9bf7c38e6fb7b92272a390df87507e30
This commit is contained in:
@@ -363,7 +363,10 @@ func (m *syspropLibrary) ShouldSupportSdkVersion(ctx android.BaseModuleContext,
|
||||
// sysprop_library creates schematized APIs from sysprop description files (.sysprop).
|
||||
// Both Java and C++ modules can link against sysprop_library, and API stability check
|
||||
// against latest APIs (see build/soong/scripts/freeze-sysprop-api-files.sh)
|
||||
// is performed.
|
||||
// is performed. Note that the generated C++ module has its name prefixed with
|
||||
// `lib`, and it is this module that should be depended on from other C++
|
||||
// modules; i.e., if the sysprop_library module is named `foo`, C++ modules
|
||||
// should depend on `libfoo`.
|
||||
func syspropLibraryFactory() android.Module {
|
||||
m := &syspropLibrary{}
|
||||
|
||||
|
Reference in New Issue
Block a user