1,
http://www.ibm.com/developerworks/cn/opensource/os-cn-android-build/
2,
Typically Android.mk start with (sets current dir and clears all other LOCAL_* variables and make them having default values)
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
Set required LOCAL_ variables:
- list of files to be included into the build
LOCAL_SRC_FILES
- the module name (as it will appear in the final output, should be unique through the Android.mk files)
LOCAL_MODULE
LOCAL_JAVA_LIBRARIES
3,Android helper targets – build targets
- Various targets are defined by Android to build Android Linux executable, shared dynamic library, static library, java library, Android application and etc.
- The targets are a set of required Makefile instructions based on values of LOCAL_* variables.
- You can make use of a target using
include $(BUILD_TARGET_NAME)
- Before start setting LOCAL_* variables you need to clear them from previous makefile. Use include $(CLEAR_VARS). This will clear all LOCAL_* variables. This command doesn’t affect any of the TARGET_* or PRODUCT_* variables.
- returns current dir name in which you Makefile is located.
$(call my-dir)
- finds all JAVA files available in the folder <src> and all its subfolders. Usually used to form LOCAL_SRC_FILES variable – as it defines the files to be included into the build
$(call all-java-files-under, <src>)
- the same as previous but finds c files.
$(call all-c-files-under, <src>)
- the same as previous but it finds *.aidl files to be passed to AIDL tool.
$(call all-Iaidl-files-under, <src>)
- finds all makefiles available under the <folder>
$(call all-makefiles-under, <folder>)
- finds the folder where the build output will be stored
$(call intermediates-dir-for, <class>, <app_name>, <host or target>, <common?> )
Many other target available. Check them in build/core/definitions.mk file.
文件名 | 说明 |
---|---|
host_static_library.mk | 定义了如何编译主机上的静态库。 |
host_shared_library.mk | 定义了如何编译主机上的共享库。 |
static_library.mk | 定义了如何编译设备上的静态库。 |
shared_library.mk | 定义了如何编译设备上的共享库。 |
executable.mk | 定义了如何编译设备上的可执行文件。 |
host_executable.mk | 定义了如何编译主机上的可执行文件。 |
package.mk | 定义了如何编译 APK 文件。 |
prebuilt.mk | 定义了如何处理一个已经编译好的文件 ( 例如 Jar 包 )。 |
multi_prebuilt.mk | 定义了如何处理一个或多个已编译文件,该文件的实现依赖 prebuilt.mk。 |
host_prebuilt.mk | 处理一个或多个主机上使用的已编译文件,该文件的实现依赖 multi_prebuilt.mk。 |
java_library.mk | 定义了如何编译设备上的共享 Java 库。 |
static_java_library.mk | 定义了如何编译设备上的静态 Java 库。 |
host_java_library.mk | 定义了如何编译主机上的共享 Java 库。 |
不同类型的模块的编译过程会有一些相同的步骤,例如:编译一个 Java 库和编译一个 APK 文件都需要定义如何编译 Java 文件。因此,表 3 中的这些 Make 文件的定义中会包含一些共同的代码逻辑。为了减少代码冗余,需要将共同的代码复用起来,复用的方式是将共同代码放到专门的文件中,然后在其他文件中包含这些文件的方式来实现的。这些包含关系如图 5 所示。由于篇幅关系,这里就不再对其他文件做详细描述(其实这些文件从文件名称中就可以大致猜出其作用)。