基于 AndroidSDK 的 Ant 环境配置 (一)

最近公司有在各大市场上架产品的打算,所以这几天都在配置 Ant 和 Eclipse .总结下步骤吧.

准备工作

环境配置

Java 环境配置

下载 JDK ,建议去 Orcale (地址)下载,国内的会附赠百毒全家桶(全家桶说明).
配置就不说了,网上一抓一大把.

AndroidSDK 的配置

新建系统变量ANDROID_HOME,变量值为你的 AndroidSDK 路径.
修改系统变量Path,追加变量值%ANDROID_HOME%\tools和%ANDROID_HOME%\platform-tools(用;分隔开来).

更新项目

更新项目,创建build.xml, local.properties 和 ant.properties文件.

在终端下,执行android update project -p 项目路径 [-t API版本号] [-n 项目名称]

\目标 API 版本号是可选项,要查看当前环境可用的 API 版本号,可以在终端下输入android list target查看.*

\项目名称是可选项,如不填写将以启动的Activity命名.*

此操作会自动将项目和项目依赖添加build.xml, local.properties和project.properties, ant.properties需要自己生成.

配置

查看build.xml

接下来我们来看看build.xml.

<?xml version="1.0" encoding="UTF-8"?>
<project name="MainActivity" default="help">

    <!-- The local.properties file is created and updated by the 'android' tool.
         It contains the path to the SDK. It should *NOT* be checked into
         Version Control Systems. -->
    <property file="local.properties" />

    <!-- The ant.properties file can be created by you. It is only edited by the
         'android' tool to add properties to it.
         This is the place to change some Ant specific build properties.
         Here are some properties you may want to change/update:

         source.dir
             The name of the source directory. Default is 'src'.
         out.dir
             The name of the output directory. Default is 'bin'.

         For other overridable properties, look at the beginning of the rules
         files in the SDK, at tools/ant/build.xml

         Properties related to the SDK location or the project target should
         be updated using the 'android' tool with the 'update' action.

         This file is an integral part of the build system for your
         application and should be checked into Version Control Systems.

         -->
    <property file="ant.properties" />

    <!-- if sdk.dir was not set from one of the property file, then
         get it from the ANDROID_HOME env var.
         This must be done before we load project.properties since
         the proguard config can use sdk.dir -->
    <property environment="env" />
    <condition property="sdk.dir" value="${env.ANDROID_HOME}">
        <isset property="env.ANDROID_HOME" />
    </condition>

    <!-- The project.properties file is created and updated by the 'android'
         tool, as well as ADT.

         This contains project specific properties such as project target, and library
         dependencies. Lower level build properties are stored in ant.properties
         (or in .classpath for Eclipse projects).

         This file is an integral part of the build system for your
         application and should be checked into Version Control Systems. -->
    <loadproperties srcFile="project.properties" />

    <!-- quick check on sdk.dir -->
    <fail
            message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable."
            unless="sdk.dir"
    />

    <!--
        Import per project custom build rules if present at the root of the project.
        This is the place to put custom intermediary targets such as:
            -pre-build
            -pre-compile
            -post-compile (This is typically used for code obfuscation.
                           Compiled code location: ${out.classes.absolute.dir}
                           If this is not done in place, override ${out.dex.input.absolute.dir})
            -post-package
            -post-build
            -pre-clean
    -->
    <import file="custom_rules.xml" optional="true" />

    <!-- Import the actual build file.

         To customize existing targets, there are two options:
         - Customize only one target:
             - copy/paste the target into this file, *before* the
               <import> task.
             - customize it to your needs.
         - Customize the whole content of build.xml
             - copy/paste the content of the rules files (minus the top node)
               into this file, replacing the <import> task.
             - customize to your needs.

         ***********************
         ****** IMPORTANT ******
         ***********************
         In all cases you must update the value of version-tag below to read 'custom' instead of an integer,
         in order to avoid having your file be overridden by tools such as "android update project"
    -->
    <!-- version-tag: 1 -->
    <import file="${sdk.dir}/tools/ant/build.xml" />

</project>

这是自动生成的build.xml文件,好像有点长,把注释删除掉好了.

<?xml version="1.0" encoding="UTF-8"?>
<project name="MainActivity" default="help">

    <property file="local.properties" />

    <property file="ant.properties" />

    <property environment="env" />
    <condition property="sdk.dir" value="${env.ANDROID_HOME}">
        <isset property="env.ANDROID_HOME" />
    </condition>

    <loadproperties srcFile="project.properties" />

    <!-- quick check on sdk.dir -->
    <fail
            message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable."
            unless="sdk.dir"
    />

    <import file="custom_rules.xml" optional="true" />

    <import file="${sdk.dir}/tools/ant/build.xml" />

</project>

• project的name属性是编译生成文件的名称
• default是执行后默认进行的操作
• property是外部文件引用

从文件中可以看到当 Ant 开始编译时,会先读取local.properties和ant.properties
中的配置,然后开始检查 AndroidSDK 路径,设定项目目标平台,最后开始读取 AndroidSDK 内置的编译选项.

这个时候我们就可以在 Eclipse 中刷新项目,右键build.xml->Ant Build...来选择编译选项.

AndroidSDK 内置了常用的编译选项,我们可以从中选择自己需要的编译选项.

常用的编译选项:

• clean: 清除先前生成的文件.
• debug: 使用debug签名编译程序.
• release: 正式编译,需要指定签名和密码等.
• uninstall: 卸载已安装的程序
• install*: 安装程序(debug, release, instrumented, test and tested)

将编译选项按流程排序后就可应用并运行了,如果不更改编译设置的话可以使用快捷键alt+shift+x来直接编译.

(未完)