android_makefile(国外英文资料).doc

android_makefile The Introduction: The android.mk compiler is used to describe your C, C + + source code files to the Android NDK, and this document describes its syntax. Before you read the following, assume that you have read the docs/overview.txt file and understand their feet and USES. An overview An Android.mk file is used to describe your source code to the compiled system. Specifically: (1) this file is a small part of the GNU Makefile, which will be parsed by the compiler system once or more. Therefore, you should minimize the variables you declare, and dont assume that certain variables will not be defined during parsing. (2) the syntax of this file allows you to organize your source code into modules, one of which is one of the following types: 1) static library 2) Shared library, and only the Shared libraries to be installed/copied to your application package, although the static library can be used to generate Shared libraries. You can define one or more modules in each Android.mk file, and you can use the same source file in several modules. (1) the compile system deals with many details for you. For example, you dont need to list header files and dependent files in your Android.mk. The NDK compiler will automate these issues for you. This also means that after upgrading the NDK, you should be supported by the new toolchain/platform and do not need to change your Android.mk file. Note that the syntax with the public release of the Android platform open source code is very close, but build system to realize their way is different, this is deliberately designed so that, can let application developers reuse external library source code easier. Before describing the grammar details, lets take a look at a simple hello world example, such as the following file: Sources/helloworld/helloworld. C Sources/helloworld/Android. Mk helloworld. C is a JNI Shared library that implements the native method of returning the hello world string. The corresponding Android.mk