AndroidBoard.mk vs. BoardConfig.mk
posted May 28, 2011, 2:36 AM by Ilya Yukhnovskiy
BoardConfig.mk is intended to contain HW specific configurations and build flags.
It should define low level HW features available for your device
It should define how the final output is packaged and what is included there (boot loader, kernel and etc)
AndroidBoard.mk configures Android Platform on top of your HW Board
Defines the files that are produced during the build and included into the Android platform build
Defines the files various Android partitions
Defines set of the applications to be packaged for your product
Can define Android platform features that needs to be the part of your product build.
posted May 28, 2011, 2:36 AM by Ilya Yukhnovskiy
BoardConfig.mk is intended to contain HW specific configurations and build flags.
It should define low level HW features available for your device
It should define how the final output is packaged and what is included there (boot loader, kernel and etc)
AndroidBoard.mk configures Android Platform on top of your HW Board
Defines the files that are produced during the build and included into the Android platform build
Defines the files various Android partitions
Defines set of the applications to be packaged for your product
Can define Android platform features that needs to be the part of your product build.
扫一扫
3528
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
