本文深入解析Android开发中使用不同的Build Flavors（如eng、user、userdebug）来构建不同版本的应用程序，解释了如何根据产品的最终目标选择正确的安装类型，并详细说明了这些配置之间的区别和用法。
LOCAL_MODULE_TAGS ：=user eng tests optional
user: 指该模块只在user版本下才编译
eng: 指该模块只在eng版本下才编译
tests: 指该模块只在tests版本下才编译
optional:指该模块在所有版本下都编译
eng This is the default flavor. A plain "make" is the same as "make eng". droid is an alias for eng.
* Installs modules tagged with: eng, debug, user, and/or development.
* 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.
Build flavors/types
When building for a particular product, it's often useful to have minorvariations on what is ultimately the final release build. These are thecurrently-defined "flavors" or "types" (we need to settle on a real namefor these).
eng | This is the default flavor. A plain "make" is the same as "make eng". droid is an alias for eng.
|
user | "make user" This is the flavor intended to be the final release bits.
|
userdebug | "make userdebug" The same as
|
If you build one flavor and then want to build another, you should run"make installclean" between the two makes to guarantee thatyou don't pick up files installed by the previous flavor. "makeclean" will also suffice, but it takes a lot longer.
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
