Eclipse下配置Ant脚本 自动打包带签名的Android apk

Posted yanzi1225627

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了Eclipse下配置Ant脚本 自动打包带签名的Android apk相关的知识,希望对你有一定的参考价值。

虽然eclipse很少用了,但是在古老的项目上还是会用到。一个麻烦事是打带签名包的时候,非常不方便。下边纪录下配置ant,自动打包带签名apk的过程,作为备忘。(PC环境为MAC)

1,第一步得安ant,下载对应安装包,解压后配置环境变量:

export ANT_HOME="/Users/yanzi/work/apache-ant-1.9.4"

export PATH=${PATH}:${ANT_HOME}/bin

通过which ant检查是否安装成功。


2,在项目目录下运行:android update project -p ./  如果有依赖包,就到每个依赖包目录下再运行下这个命令。运行完这个命令后会多两个文件:build.xml 和 local.properties

local.properties文件内容:

sdk.dir=/Users/yanzi/work/android-tool/android-sdk-macosx


build.xml文件内容:

<?xml version="1.0" encoding="UTF-8"?>
<project name="TongCheng" 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>
这两个文件都不用动,最上面project的name里写上自己想要的名字。然后项目根目录下新建个ant.properties,内容如下:

# This file is used to override default values used by the Ant build system.
#
# This file must be checked in Version Control Systems, as it is
# integral to the build system of your project.

# This file is only used by the Ant script.

# You can use this to override default values such as
#  'source.dir' for the location of your java source folder and
#  'out.dir' for the location of your output folder.

# You can also use it define how the release builds are signed by declaring
# the following properties:
#  'key.store' for the location of your keystore and
#  'key.alias' for the name of the key to use.
# The password will be asked during the build when you use the 'release' target.

key.alias=com.tongcheng
key.store=tongcheng.keystore
key.store.password=12377778
key.alias.password=12377778
配置上keystore的相关信息。

这样先执行ant clean,然后执行ant release就ok了!

3,当然为了更爽,你还需要下面这个脚本:

vim release.sh,内容如下:

echo -----------------start---------
start=$(date +%s)
ant clean
ant release
adb uninstall com.android.tongcheng
adb install bin/TongCheng-release.apk
end=$(date +%s)
echo "----over,耗时$[${end} - ${start}]秒---"


之后每次想安装带签名的包,直接./release.sh即可!

需要多渠道包的请参考 此篇 文章


以上是关于Eclipse下配置Ant脚本 自动打包带签名的Android apk的主要内容,如果未能解决你的问题,请参考以下文章

Eclipse—Ant批量打包

用Ant给Unity3D导出Eclipse工程打包APK

用Ant手动打包android程序

Android自动化构建之Ant多渠道打包实践(上)

Eclipse下用ant打包时怎么添加jar包

使用Gradle与Ant实现可配置不同环境的自动打包