Bootstrap

Android系统开发编译环境配置 (感觉好经典的系列)(其二)

创建一个新的 Android 产品项目

google网站上下载的android源代码编译时默认是编译google设定的产品,如果要开发自己的产品,

则需要重新定义一个产品项目,过程如下:

首先我们定义产品的规格,举例如下:

公司名称 ardent

产品名称 MTP

主板名称 merlin

然后安装下面的步骤新建产品项目:

(1)在源代码目录下创建一个用户目录

mkdir vendor


(2)在用户目录下创建一个公司目录

mkdir vendor/merlin


(3)在公司目录下创建一个products目录

mkdir vendor/merlin/products


(4)在上面创建的products下创建一个产品makefile文件MTP.mk,内容如下:

PRODUCT_PACKAGES := \

AlarmClock \

Email \

Fallback \

Launcher2 \

Music \

Camera \

Settings \

LatinIME \

NotePad \

SoundRecorder \

Bluetooth \

CertInstaller \

DeskClock


$(call inherit-product, $(SRC_TARGET_DIR)/product/core.mk)

#

# Overrides

PRODUCT_MANUFACTURER := ardent

PRODUCT_BRAND := ardent

PRODUCT_NAME := MTP

PRODUCT_MODEL := MultiMedia Touch Phone

PRODUCT_DEVICE := merlin

PRODUCT_LOCALES := zh_CN

产品makefile文件的编写有一套规则,详细情况见此文后面的补充内容。


(5)vendor/merlin/products目录下创建一个AndroidProducts.mk文件,定义Android产品配置文件的路径,具体如下:

PRODUCT_MAKEFILES := \

$(LOCAL_DIR)/MTP.mk


(6)在公司目录下创建一个主板目录

mkdir vendor/ardent/merlin


(7)在主板目录下新建一个主板配置文件BoardConfig.mk,内容如下:

TARGET_NO_BOOTLOADER := true

TARGET_NO_KERNEL := true

TARGET_CPU_ABI := armeabi

BOARD_USES_GENERIC_AUDIO := true

USE_CAMERA_STUB := true


(8)如果你希望修改系统属性,则可以在主板目录下新建一个system.prop文件,该文件中可以修改系统属性,举例如下:

# system.prop for

# This overrides settings in the products/generic/system.prop file

#

# rild.libpath=/system/lib/libreference-ril.so

# rild.libargs=-d /dev/ttyS0


(9)在主板目录下建议一个Android的主板配置文件AndroidBoard.mk,此文件是编译系统接口文件,内容如下:

# make file for new hardware from

#

LOCAL_PATH := $(call my-dir)


#

# this is here to use the pre-built kernel

ifeq ($(TARGET_PREBUILT_KERNEL),)

TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/kernel

endif


file := $(INSTALLED_KERNEL_TARGET)

ALL_PREBUILT += $(file)

$(file): $(TARGET_PREBUILT_KERNEL) | $(ACP)

$(transform-prebuilt-to-target)


#

# no boot loader, so we don't need any of that stuff..

#

LOCAL_PATH := vendor/ardent/merlin

include $(CLEAR_VARS)

#

# include more board specific stuff here? Such as Audio parameters.

#


(10)编译新的项目

. build/envsetup.sh

make PRODUCT-MTP-user


补充内容:

(1)上面的新建的几个文件的编写可以参考build/target/board/generic目录下的AndroidBoard.mkBoardConfig.mksystem.prop


(2)产品makefile的编写规则,变量定义解释如下:

PRODUCT_NAME 终端用户可见的产品名称,对应到“Settings“中的“About the phone”信息

PRODUCT_MODEL End-user-visible name for the end product

PRODUCT_LOCALES 1个以空格分隔开的两个字母的语言码加上2字节的国家码的列表,影响到"Settings"中的语言,时间,日期和货币格式设置,

举例:en_GB de_DE es_ES fr_CA

PRODUCT_PACKAGES 需要安装的APK应用程序列表

PRODUCT_DEVICE 工作设计名称,即主板名称

PRODUCT_MANUFACTURER 生产厂家

PRODUCT_BRAND 软件设计针对的客户品牌

PRODUCT_PROPERTY_OVERRIDES "key=value"为格式的属性列表

PRODUCT_COPY_FILES 文件复制列表,格式为“原文件路径:目的文件路径”,编译过程中会按照此规则复制文件

PRODUCT_OTA_PUBLIC_KEYS 产品的OTA公共密匙列表

PRODUCT_POLICY 声明此产品使用的政策

PRODUCT_PACKAGE_OVERLAYS 指示是否使用默认资源或添加任何产品特定的资源,例如:vendor/acme/overlay

PRODUCT_CONTRIBUTORS_FILE HTML文件中包含项目的贡献者

PRODUCT_TAGS 以空格分隔开的指定产品关键词列表


本文来自CSDN博客,转载请标明出处:ttp://blog.csdn.net/jiajie961/archive/2010/11/07/5993126.aspx


制作 ubifs 文件系统

1,安装相关的软件包

apt-get install liblzo2-dev


2,获取相关的工具mkfs.ubifsubinize

这两个工具是制作ubifs文件系统的时候用到,它们是mtd-utils工具包中的内容,mtd-utils工具包你可以从下面的网站下载和编译出来:

官方网站:http://www.linux-mtd.infradead.org/index.html

资源下载网站:http://git.infradead.org/


3,创建一个create-ubifs.sh脚本,主要是调用mkfs.ubifsubinize工具和相关参数来制作ubifs文件系统,内容如下:

#!/bin/bash


##########################################################

# Script to generate ubifs filesystem image. #

##########################################################


##### ubinize configuration file

config_file=rootfs_ubinize.cfg


##### Function to check result of the command

check_result() {

if [ $? -ne 0 ]

then

echo "FAILED"

else

echo "SUCCESSFUL"

fi

}


###### Function to check whether an application exists

check_program() {

for cmd in "$@"

do

which ${cmd} > /dev/null 2>&1

if [ $? -ne 0 ]

then

echo

echo "Cannot find command \"${cmd}\""

echo

exit 1

fi

done

}


if [ $# -ne 5 ]

then

echo

echo 'Usage: create-ubifs.sh [page_size_in_bytes] [pages_per_block] [partition_size_in_bytes] [blocks_per_device] [path_to_rootfs]'

echo

exit

fi


page_size_in_bytes=$1

echo "Page size [$page_size_in_bytes]bytes."

pages_per_block=$2

echo "Pages per block [$pages_per_block]"

partition_size_in_bytes=$3

echo "File-system partition size [$partition_size_in_bytes]bytes."

blocks_per_device=$4

echo "Blocks per device [$blocks_per_device]"

path_to_rootfs=$5


# wear_level_reserved_blocks is 1% of total blcoks per device

wear_level_reserved_blocks=`expr $blocks_per_device / 100`

echo "Reserved blocks for wear level [$wear_level_reserved_blocks]"


#logical_erase_block_size is physical erase block size minus 2 pages for UBI

logical_pages_per_block=`expr $pages_per_block - 2`

logical_erase_block_size=`expr $page_size_in_bytes \* $logical_pages_per_block`

echo "Logical erase block size [$logical_erase_block_size]bytes."


#Block size = page_size * pages_per_block

block_size=`expr $page_size_in_bytes \* $pages_per_block`

echo "Block size [$block_size]bytes."


#physical blocks on a partition = partition size / block size

partition_physical_blocks=`expr $partition_size_in_bytes / $block_size`

echo "Physical blocks in a partition [$partition_physical_blocks]"


#Logical blocks on a partition = physical blocks on a partitiion - reserved for wear level

patition_logical_blocks=`expr $partition_physical_blocks - $wear_level_reserved_blocks`

echo "Logical blocks in a partition [$patition_logical_blocks]"


#File-system volume = Logical blocks in a partition * Logical erase block size

fs_vol_size=`expr $patition_logical_blocks \* $logical_erase_block_size`

echo "File-system volume [$fs_vol_size]bytes."


echo

echo "Generating configuration file..."

echo "[rootfs-volume]" > $config_file

echo "mode=ubi" >> $config_file

echo "image=rootfs_ubifs.img" >> $config_file

echo "vol_id=0" >> $config_file

echo "vol_size=$fs_vol_size" >> $config_file

echo "vol_type=dynamic" >> $config_file

echo "vol_name=system" >> $config_file

echo


# Note: Check necessary program for installation

#echo -n "Checking necessary program for installation......"

#check_program mkfs.ubifs ubinize

#echo "Done"


#Generate ubifs image

echo -n "Generating ubifs..."

./mkfs.ubifs -x lzo -m $page_size_in_bytes -e $logical_erase_block_size -c $patition_logical_blocks -o rootfs_ubifs.img -d $path_to_rootfs

check_result

echo -n "Generating ubi image out of the ubifs..."

./ubinize -o ubi.img -m $page_size_in_bytes -p $block_size -s $page_size_in_bytes $config_file -v

check_result


rm -f rootfs_ubifs.img

rm -f $config_file


(4)mkfs.ubifsubinize以及create-ubifs.sh放置在同一目录下,然后调用create-ubifs.sh即可创建ubifs文件系统,create-ubifs.sh用法如下:

create-ubifs.sh page_size_in_bytes(页大小) pages_per_block(每个扇区的页数量) partition_size_in_bytes(分区大小) blocks_per_device(扇区数量) path_to_rootfs(文件系统路径)

举例如下:

./create-ubifs.sh 2048 64 83886080 4096 ./rootfs

上面命令的意思是调用create-ubifs.sh将当前目录下的rootfs文件夹的内容制作成ubifs文件系统,nand flash的页大小为2k,每个扇区有64页,

总共有4096个扇区,要制作的文件系统的大小为83886080字节。


本文来自CSDN博客,转载请标明出处:http://blog.csdn.net/jiajie961/archive/2010/11/08/5994713.aspx


android 编译系统 makefile(Android.mk) 写法

android编译系统的makefile文件Android.mk写法如下


(1)Android.mk文件首先需要指定LOCAL_PATH变量,用于查找源文件。由于一般情况下

Android.mk和需要编译的源文件在同一目录下,所以定义成如下形式:

LOCAL_PATH:=$(call my-dir)

上面的语句的意思是将LOCAL_PATH变量定义成本文件所在目录路径。


(2)Android.mk中可以定义多个编译模块,每个编译模块都是以include $(CLEAR_VARS)开始

include $(BUILD_XXX)结束。

include $(CLEAR_VARS)

CLEAR_VARS由编译系统提供,指定让GNU MAKEFILE为你清除除LOCAL_PATH以外的所有LOCAL_XXX变量,

LOCAL_MODULELOCAL_SRC_FILESLOCAL_SHARED_LIBRARIESLOCAL_STATIC_LIBRARIES等。

include $(BUILD_STATIC_LIBRARY)表示编译成静态库

include $(BUILD_SHARED_LIBRARY)表示编译成动态库。

include $(BUILD_EXECUTABLE)表示编译成可执行程序


(3)举例如下(frameworks/base/libs/audioflinger/Android.mk)

LOCAL_PATH:= $(call my-dir)

include $(CLEAR_VARS) 模块一

ifeq ($(AUDIO_POLICY_TEST),true)

ENABLE_AUDIO_DUMP := true

endif

LOCAL_SRC_FILES:= \

AudioHardwareGeneric.cpp \

AudioHardwareStub.cpp \

AudioHardwareInterface.cpp

ifeq ($(ENABLE_AUDIO_DUMP),true)

LOCAL_SRC_FILES += AudioDumpInterface.cpp

LOCAL_CFLAGS += -DENABLE_AUDIO_DUMP

endif

LOCAL_SHARED_LIBRARIES := \

libcutils \

libutils \

libbinder \

libmedia \

libhardware_legacy

ifeq ($(strip $(BOARD_USES_GENERIC_AUDIO)),true)

LOCAL_CFLAGS += -DGENERIC_AUDIO

endif

LOCAL_MODULE:= libaudiointerface

ifeq ($(BOARD_HAVE_BLUETOOTH),true)

LOCAL_SRC_FILES += A2dpAudioInterface.cpp

LOCAL_SHARED_LIBRARIES += liba2dp

LOCAL_CFLAGS += -DWITH_BLUETOOTH -DWITH_A2DP

LOCAL_C_INCLUDES += $(call include-path-for, bluez)

endif

include $(BUILD_STATIC_LIBRARY) 模块一编译成静态库

include $(CLEAR_VARS) 模块二

LOCAL_SRC_FILES:= \

AudioPolicyManagerBase.cpp

LOCAL_SHARED_LIBRARIES := \

libcutils \

libutils \

libmedia

ifeq ($(TARGET_SIMULATOR),true)

LOCAL_LDLIBS += -ldl

else

LOCAL_SHARED_LIBRARIES += libdl

endif

LOCAL_MODULE:= libaudiopolicybase

ifeq ($(BOARD_HAVE_BLUETOOTH),true)

LOCAL_CFLAGS += -DWITH_A2DP

endif

ifeq ($(AUDIO_POLICY_TEST),true)

LOCAL_CFLAGS += -DAUDIO_POLICY_TEST

endif

include $(BUILD_STATIC_LIBRARY) 模块二编译成静态库

include $(CLEAR_VARS) 模块三

LOCAL_SRC_FILES:= \

AudioFlinger.cpp \

AudioMixer.cpp.arm \

AudioResampler.cpp.arm \

AudioResamplerSinc.cpp.arm \

AudioResamplerCubic.cpp.arm \

AudioPolicyService.cpp

LOCAL_SHARED_LIBRARIES := \

libcutils \

libutils \

libbinder \

libmedia \

libhardware_legacy

ifeq ($(strip $(BOARD_USES_GENERIC_AUDIO)),true)

LOCAL_STATIC_LIBRARIES += libaudiointerface libaudiopolicybase

LOCAL_CFLAGS += -DGENERIC_AUDIO

else

LOCAL_SHARED_LIBRARIES += libaudio libaudiopolicy

endif

ifeq ($(TARGET_SIMULATOR),true)

LOCAL_LDLIBS += -ldl

else

LOCAL_SHARED_LIBRARIES += libdl

endif

LOCAL_MODULE:= libaudioflinger

ifeq ($(BOARD_HAVE_BLUETOOTH),true)

LOCAL_CFLAGS += -DWITH_BLUETOOTH -DWITH_A2DP

LOCAL_SHARED_LIBRARIES += liba2dp

endif

ifeq ($(AUDIO_POLICY_TEST),true)

LOCAL_CFLAGS += -DAUDIO_POLICY_TEST

endif

ifeq ($(TARGET_SIMULATOR),true)

ifeq ($(HOST_OS),linux)

LOCAL_LDLIBS += -lrt -lpthread

endif

endif

ifeq ($(BOARD_USE_LVMX),true)

LOCAL_CFLAGS += -DLVMX

LOCAL_C_INCLUDES += vendor/nxp

LOCAL_STATIC_LIBRARIES += liblifevibes

LOCAL_SHARED_LIBRARIES += liblvmxservice

# LOCAL_SHARED_LIBRARIES += liblvmxipc

endif

include $(BUILD_SHARED_LIBRARY) 模块三编译成动态库



(4)编译一个应用程序(APK)

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

# Build all java files in the java subdirectory

LOCAL_SRC_FILES := $(call all-subdir-java-files)

# Name of the APK to build

LOCAL_PACKAGE_NAME := LocalPackage

# Tell it to build an APK

include $(BUILD_PACKAGE)


(5)编译一个依赖于静态Java(static.jar)的应用程序

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

# List of static libraries to include in the package

LOCAL_STATIC_JAVA_LIBRARIES := static-library

# Build all java files in the java subdirectory

LOCAL_SRC_FILES := $(call all-subdir-java-files)

# Name of the APK to build

LOCAL_PACKAGE_NAME := LocalPackage

# Tell it to build an APK

include $(BUILD_PACKAGE)


(6)编译一个需要用平台的key签名的应用程序

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

# Build all java files in the java subdirectory

LOCAL_SRC_FILES := $(call all-subdir-java-files)

# Name of the APK to build

LOCAL_PACKAGE_NAME := LocalPackage

LOCAL_CERTIFICATE := platform

# Tell it to build an APK

include $(BUILD_PACKAGE)



(7)编译一个需要用特定key前面的应用程序

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

# Build all java files in the java subdirectory

LOCAL_SRC_FILES := $(call all-subdir-java-files)

# Name of the APK to build

LOCAL_PACKAGE_NAME := LocalPackage

LOCAL_CERTIFICATE := vendor/example/certs/app

# Tell it to build an APK

include $(BUILD_PACKAGE)


(8)添加一个预编译应用程序

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

# Module name should match apk name to be installed.

LOCAL_MODULE := LocalModuleName

LOCAL_SRC_FILES := $(LOCAL_MODULE).apk

LOCAL_MODULE_CLASS := APPS

LOCAL_MODULE_SUFFIX := $(COMMON_ANDROID_PACKAGE_SUFFIX)

include $(BUILD_PREBUILT)


(9)添加一个静态JAVA

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

# Build all java files in the java subdirectory

LOCAL_SRC_FILES := $(call all-subdir-java-files)

# Any libraries that this library depends on

LOCAL_JAVA_LIBRARIES := android.test.runner

# The name of the jar file to create

LOCAL_MODULE := sample

# Build a static jar file.

include $(BUILD_STATIC_JAVA_LIBRARY)


(10)Android.mk的编译模块中间可以定义相关的编译内容,也就是指定相关的变量如下:

LOCAL_AAPT_FLAGS


LOCAL_ACP_UNAVAILABLE


LOCAL_ADDITIONAL_JAVA_DIR

LOCAL_AIDL_INCLUDES


LOCAL_ALLOW_UNDEFINED_SYMBOLS


LOCAL_ARM_MODE


LOCAL_ASFLAGS


LOCAL_ASSET_DIR


LOCAL_ASSET_FILES Android.mk文件中编译应用程序(BUILD_PACKAGE)时设置此变量,表示资源文件,

通常会定义成LOCAL_ASSET_FILES += $(call find-subdir-assets)

LOCAL_BUILT_MODULE_STEM

LOCAL_C_INCLUDES 额外的C/C++编译头文件路径,用LOCAL_PATH表示本文件所在目录

举例如下:

LOCAL_C_INCLUDES += extlibs/zlib-1.2.3

LOCAL_C_INCLUDES += $(LOCAL_PATH)/src

LOCAL_CC 指定C编译器


LOCAL_CERTIFICATE 签名认证


LOCAL_CFLAGS C/C++编译器定义额外的标志(如宏定义),举例:LOCAL_CFLAGS += -DLIBUTILS_NATIVE=1

LOCAL_CLASSPATH


LOCAL_COMPRESS_MODULE_SYMBOLS


LOCAL_COPY_HEADERS install应用程序时需要复制的头文件,必须同时定义LOCAL_COPY_HEADERS_TO

LOCAL_COPY_HEADERS_TO install应用程序时复制头文件的目的路径


LOCAL_CPP_EXTENSION 如果你的C++文件不是以cpp为文件后缀,你可以通过LOCAL_CPP_EXTENSION指定C++文件后缀名

如:LOCAL_CPP_EXTENSION := .cc

注意统一模块中C++文件后缀必须保持一致。


LOCAL_CPPFLAGS 传递额外的标志给C++编译器,如:LOCAL_CPPFLAGS += -ffriend-injection


LOCAL_CXX 指定C++编译器

LOCAL_DX_FLAGS


LOCAL_EXPORT_PACKAGE_RESOURCES


LOCAL_FORCE_STATIC_EXECUTABLE 如果编译的可执行程序要进行静态链接(执行时不依赖于任何动态库),则设置LOCAL_FORCE_STATIC_EXECUTABLE:=true

目前只有libc有静态库形式,这个只有文件系统中/sbin目录下的应用程序会用到,这个目录下的应用程序在运行时通常

文件系统的其它部分还没有加载,所以必须进行静态链接。

LOCAL_GENERATED_SOURCES

LOCAL_INSTRUMENTATION_FOR


LOCAL_INSTRUMENTATION_FOR_PACKAGE_NAME


LOCAL_INTERMEDIATE_SOURCES


LOCAL_INTERMEDIATE_TARGETS


LOCAL_IS_HOST_MODULE


LOCAL_JAR_MANIFEST


LOCAL_JARJAR_RULES


LOCAL_JAVA_LIBRARIES 编译java应用程序和库的时候指定包含的java类库,目前有coreframework两种

多数情况下定义成:LOCAL_JAVA_LIBRARIES := core framework

注意LOCAL_JAVA_LIBRARIES不是必须的,而且编译APK时不允许定义(系统会自动添加)

LOCAL_JAVA_RESOURCE_DIRS


LOCAL_JAVA_RESOURCE_FILES


LOCAL_JNI_SHARED_LIBRARIES


LOCAL_LDFLAGS 传递额外的参数给连接器(务必注意参数的顺序)

LOCAL_LDLIBS 为可执行程序或者库的编译指定额外的库,指定库以"-lxxx"格式,举例:

LOCAL_LDLIBS += -lcurses -lpthread

LOCAL_LDLIBS += -Wl,-z,origin

LOCAL_MODULE 生成的模块的名称(注意应用程序名称用LOCAL_PACKAGE_NAME而不是LOCAL_MODULE)


LOCAL_MODULE_PATH 生成模块的路径

LOCAL_MODULE_STEM

LOCAL_MODULE_TAGS 生成模块的标记

LOCAL_NO_DEFAULT_COMPILER_FLAGS


LOCAL_NO_EMMA_COMPILE


LOCAL_NO_EMMA_INSTRUMENT


LOCAL_NO_STANDARD_LIBRARIES


LOCAL_OVERRIDES_PACKAGES


LOCAL_PACKAGE_NAME APK应用程序的名称


LOCAL_POST_PROCESS_COMMAND

LOCAL_PREBUILT_EXECUTABLES 预编译including $(BUILD_PREBUILT)或者$(BUILD_HOST_PREBUILT)时所用,指定需要复制的可执行文件


LOCAL_PREBUILT_JAVA_LIBRARIES


LOCAL_PREBUILT_LIBS 预编译including $(BUILD_PREBUILT)或者$(BUILD_HOST_PREBUILT)时所用指定需要复制的库.


LOCAL_PREBUILT_OBJ_FILES


LOCAL_PREBUILT_STATIC_JAVA_LIBRARIES

LOCAL_PRELINK_MODULE 是否需要预连接处理(默认需要,用来做动态库优化)


LOCAL_REQUIRED_MODULES 指定模块运行所依赖的模块(模块安装时将会同步安装它所依赖的模块)

LOCAL_RESOURCE_DIR


LOCAL_SDK_VERSION


LOCAL_SHARED_LIBRARIES 可链接动态库

LOCAL_SRC_FILES 编译源文件


LOCAL_STATIC_JAVA_LIBRARIES


LOCAL_STATIC_LIBRARIES 可链接静态库

LOCAL_UNINSTALLABLE_MODULE


LOCAL_UNSTRIPPED_PATH

LOCAL_WHOLE_STATIC_LIBRARIES 指定模块所需要载入的完整静态库(这些精通库在链接是不允许链接器删除其中无用的代码)

LOCAL_YACCFLAGS

OVERRIDE_BUILT_MODULE_PATH


本文来自CSDN博客,转载请标明出处:http://blog.csdn.net/jiajie961/archive/2010/11/09/5997147.aspx


;