android自动打包方法(ant+proguard+签名)

浏览数：16 / 时间：2015年06月11日

前段时间做了一个android的网游项目，现在优化减少体积和防止别人反编译，需要把编译后.class进行混淆，开始在网上看了一些关于 ProGuard的介绍，基本上都是使用ADT自带的打包方式，那个打包方式太慢了，还要手工输密码，一个字烦。

于是开始寻找ant+proguard+签名的打包方式，遗憾的是资料不是缺手就是断脚。

好吧，看来得食自己了，！@#￥@#！@#！@##￥@#￥！@#@ 转眼一周，我++，终于把东西搞出来

ps：我们项目还有一个特殊需求，要把版本号，推广ID打到包里去，方便做推广什么的。这里可以用replace的方法对string.xml进行修改

好吧，废话不说了，直接上build文件

1. [代码][xml]代码跳至 [1] [全屏预览]

<?xml version="1.0" encoding="UTF-8"?>

<!--

default.properties 内容

target=android-4

proguard.config=proguard.cfg

-->

<!-- Custom Android task to deal with the project target, and import the

proper rules.

This requires ant 1.6.0 or above. -->

</path>

<!-- Tells adb which device to target. You can change this from the command line

by invoking "ant -Dadb.device.arg=-d" for device "ant -Dadb.device.arg=-e" for

the emulator. -->

<!-- create a path with all the jar files, from the main project and the

libraries -->

</path>

<!-- The final package file to generate

These can be overridden by setting them earlier to

different values -->

<!-- set some properties used for filtering/override. If those weren‘t defined

before, then this will create them with empty values, which are then ignored

by the custom tasks receiving them. -->

<!-- This is needed by emma as it uses multilevel verbosity instead of simple ‘true‘ or ‘false‘

The property ‘verbosity‘ is not user configurable and depends exclusively on ‘verbose‘

value.-->

</condition>

<!-- This is needed to switch verbosity of zipalign. Depends exclusively on ‘verbose‘

-->

</condition>

</condition>

<and>

</and>

</condition>

<and>

</and>

</condition>

</condition>

</path>

<!-- Configurable macro, which allows to pass as parameters output directory,

output dex filename and external libraries to dex (optional) -->

<!-- sets the primary input for dex. If a pre-dex task sets it to

something else this has no effect -->

<!-- set the secondary dx input: the project (and library) jar files

If a pre-dex task sets it to something else this has no effect -->

<if>

</condition>

<else>

</path>

</else>

</if>

<echo>Converting compiled files and external libraries into ${intermediate.dex.file}...</echo>

<extra-parameters />

<external-libs />

</apply>

</sequential>

</macrodef>

<!-- This is macro that enable passing variable list of external jar files to ApkBuilder

Example of use:

<package-helper output.filepath="/path/to/foo.apk">

<extra-jars>

</extra-jars>

</package-helper> -->

<extra-jars />

</apkbuilder>

</sequential>

</macrodef>

<!-- This is macro which zipaligns in.package and outputs it to out.package. Used by targets

debug, -debug-with-emma and release.-->

<echo>Running zip align on final apk...</echo>

</exec>

</sequential>

</macrodef>

<!-- This is macro used only for sharing code among two targets, -install and

-install-with-emma which do exactly the same but differ in dependencies -->

<echo>Installing ${out.debug.file} onto default emulator or device...</echo>

</exec>

</sequential>

</macrodef>

<echo>Creating output directories if needed...</echo>

<then>

</then>

</if>

</target>

<!-- empty default pre-build target. Create a similar target in

your build.xml and it‘ll be called instead of this one. -->

<then>

<echo>Generating R.java / Manifest.java from the resources...</echo>

</aapt>

</then>

<else>

<echo>hasCode = false. Skipping...</echo>

</else>

</if>

</target>

<then>

<echo>Compiling aidl files into Java classes...</echo>

</aidl>

</then>

<else>

<echo>hasCode = false. Skipping...</echo>

</else>

</if>

</target>

<!-- empty default pre-compile target. Create a similar target in

your build.xml and it‘ll be called instead of this one. -->

<then>

<!-- If android rules are used for a test project, its classpath should include

tested project‘s location -->

</condition>

</condition>

</classpath>

</javac>

</then>

<else>

<echo>hasCode = false. Skipping...</echo>

</else>

</if>

</target>

<!-- empty default post-compile target. Create a similar target in

your build.xml and it‘ll be called instead of this one. -->

<!-- Obfuscate target

This is only active in release builds when proguard.config is defined

in default.properties.

To replace Proguard with a different obfuscation engine:

Override the following targets in your build.xml, before the call to <setup>

-release-obfuscation-check

Check whether obfuscation should happen, and put the result in a property.

-debug-obfuscation-check

Obfuscation should not happen. Set the same property to false.

-obfuscate

** Make sure unless="do.not.compile" is used in the target definition **

check if the property set in -debug/release-obfuscation-check is set to true.

If true:

Perform obfuscation

Set property out.dex.input.absolute.dir to be the output of the obfuscation

-->

<then>

<!-- Set the android classpath Path object into a single property. It‘ll be

all the jar files separated by a platform path-separator.

-->

<!-- Build a path object with all the jar files that must be obfuscated.

This include the project compiled source code and any 3rd party jar

files. -->

</path>

<!-- Set the project jar files Path object into a single property. It‘ll be

all the jar files separated by a platform path-separator.

-->

-optimizationpasses 5

-dontusemixedcaseclassnames

-dontskipnonpubliclibraryclasses

-dontpreverify

-verbose

-repackageclasses

-allowaccessmodification

-optimizations !code/simplification/arithmetic,!field/*,!class/merging/*

-keep public class * extends android.app.Activity

-keep public class * extends android.app.Application

-keep public class * extends android.app.Service

-keep public class * extends android.content.BroadcastReceiver

-keep public class * extends android.content.ContentProvider

-keep public class com.android.vending.licensing.ILicensingService

-injars ${project.jars}

-outjars ${obfuscated.jar.file}

-libraryjars ${android.libraryjars}

</proguard>

</then>

</if>

</target>

</target>

<then>

<dex-helper />

</then>

<else>

<echo>hasCode = false. Skipping...</echo>

</else>

</if>

</target>

<then>

<!--

-->

</java>

<!--<mkdir dir="${out-folder}"/>

</then>

</if>

</target>

<!-- Puts the project‘s resources into the output package file

This actually can create multiple resource package in case

Some custom apk with specific configuration have been

declared in default.properties.

-->

<echo>Packaging resources</echo>

</aapt>

</target>

<package-helper output.filepath="${out.debug.unaligned.file}" />

</target>

<package-helper output.filepath="${out.unsigned.file}" />

</target>

</subant>

</target>

</target>

<!-- property only set in debug mode.

Useful for if/unless attributes in target node

when using Ant before 1.8 -->

</target>

<zipalign-helper in.package="${out.debug.unaligned.file}" out.package="${out.debug.file}" />

<echo>Debug Package: ${out.debug.file}</echo>

</target>

<!-- called through target ‘release‘. Only executed if the keystore and

key alias are known but not their password. -->

<echo>Gets passwords ${has.keystore} ${has.password}</echo>

</target>

<!-- called through target ‘release‘. Only executed if there‘s no

keystore/key alias set -->

<echo>No key.store and key.alias properties found in build.properties.</echo>

<echo>Please sign ${out.unsigned.file} manually</echo>

<echo>and run zipalign from the Android SDK tools.</echo>

</target>

<and>

</and>

</condition>

<then>

<!-- Secondary dx input (jar files) is empty since all the

jar files will be in the obfuscated jar -->

</then>

</if>

</target>

<!-- release mode is only valid if the manifest does not explicitly

set debuggable to true. default is false.

We actually store build.packaging.debug, not build.release -->

<then>

<echo>**** Android Manifest has debuggable=true ****</echo>

<echo>**** Doing DEBUG packaging with RELEASE keys ****</echo>

</then>

<else>

<!-- property only set in release mode.

Useful for if/unless attributes in target node

when using Ant before 1.8 -->

</else>

</if>

</target>

<!-- This runs -package-release and -release-nosign first and then runs

only if release-sign is true (set in -release-check,

called by -release-no-sign)-->

<target name="release" depends="-set-release-mode, -release-obfuscation-check, -package-release, -release-prompt-for-password, -release-nosign" if="has.keystore" description="Builds the application. The generated apk file must be signed before

it is published.">

<echo>Signing final apk...</echo>

<zipalign-helper in.package="${out.unaligned.file}" out.package="${out.release.file}" />

<echo>Release Package: ${out.release.file}</echo>

</target>

</target>

</target>

</project>

android自动打包方法(ant+proguard+签名),,5-wow.com

郑重声明：本站内容如果来自互联网及其他传播媒体，其版权均属原媒体及文章作者所有。转载目的在于传递更多信息及用于网络分享，并不代表本站赞同其观点和对其真实性负责，也不构成任何其他建议。

android自动打包方法(ant+proguard+签名)

标签： Android iOS 移动互联终端开发

android自动打包方法(ant+proguard+签名)

相关文章

随机文章

您可能还喜欢

您可能还喜欢

最新图文

您可能还喜欢

您可能还喜欢

文摘排行

文章排行

推荐文章

图文排行

推荐图文