"Set LOCAL_MODULE_TAGS to any number of whitespace-separated tags.This variable controls what build flavors the package gets included
in. For example: * user: include this in user/userdebug builds
* eng: include this in eng builds
* tests: the target is a testing target and makes it available for
tests
* optional: don't include this"Are these the same as "variants" and if so, which name would affect
the build and how? I've noticed that everything mentioned in a
product's makefile will always get built. But what gets in the final
system.img not always the same as what gets built.
in. For example: * user: include this in user/userdebug builds
* eng: include this in eng builds
* tests: the target is a testing target and makes it available for
tests
* optional: don't include this"Are these the same as "variants" and if so, which name would affect
the build and how? I've noticed that everything mentioned in a
product's makefile will always get built. But what gets in the final
system.img not always the same as what gets built.
user:
* eng:
* tests:
* optional:
怎么解释阿?
eng: 指该模块只在eng版本下才编译
tests: 指该模块只在tests版本下才编译
optional:指该模块在所有版本下都编译
* Installs non-APK modules that have no tags specified.
* Installs APKs according to the product definition files, in addition to tagged APKs.
* ro.secure=0
* ro.debuggable=1
* ro.kernel.android.checkjni=1
* adb is enabled by default. user "make user"This is the flavor intended to be the final release bits. * Installs modules tagged with user.
* Installs non-APK modules that have no tags specified.
* Installs APKs according to the product definition files; tags are ignored for APK modules.
* ro.secure=1
* ro.debuggable=0
* adb is disabled by default. userdebug "make userdebug"The same as user, except: * Also installs modules tagged with debug.
* ro.debuggable=1
* adb is enabled by default.