OLD | NEW |
(Empty) | |
| 1 <?xml version="1.0" encoding="UTF-8"?> |
| 2 <project name="Adblock Plus JNI Binding Library Tests" default="help"> |
| 3 |
| 4 <!-- The local.properties file is created and updated by the 'android' tool. |
| 5 It contains the path to the SDK. It should *NOT* be checked into |
| 6 Version Control Systems. --> |
| 7 <property file="local.properties" /> |
| 8 |
| 9 <!-- The ant.properties file can be created by you. It is only edited by the |
| 10 'android' tool to add properties to it. |
| 11 This is the place to change some Ant specific build properties. |
| 12 Here are some properties you may want to change/update: |
| 13 |
| 14 source.dir |
| 15 The name of the source directory. Default is 'src'. |
| 16 out.dir |
| 17 The name of the output directory. Default is 'bin'. |
| 18 |
| 19 For other overridable properties, look at the beginning of the rules |
| 20 files in the SDK, at tools/ant/build.xml |
| 21 |
| 22 Properties related to the SDK location or the project target should |
| 23 be updated using the 'android' tool with the 'update' action. |
| 24 |
| 25 This file is an integral part of the build system for your |
| 26 application and should be checked into Version Control Systems. |
| 27 |
| 28 --> |
| 29 <property file="ant.properties" /> |
| 30 |
| 31 <!-- if sdk.dir was not set from one of the property file, then |
| 32 get it from the ANDROID_HOME env var. |
| 33 This must be done before we load project.properties since |
| 34 the proguard config can use sdk.dir --> |
| 35 <property environment="env" /> |
| 36 <condition property="sdk.dir" value="${env.ANDROID_HOME}"> |
| 37 <isset property="env.ANDROID_HOME" /> |
| 38 </condition> |
| 39 |
| 40 <!-- The project.properties file is created and updated by the 'android' |
| 41 tool, as well as ADT. |
| 42 |
| 43 This contains project specific properties such as project target, and l
ibrary |
| 44 dependencies. Lower level build properties are stored in ant.properties |
| 45 (or in .classpath for Eclipse projects). |
| 46 |
| 47 This file is an integral part of the build system for your |
| 48 application and should be checked into Version Control Systems. --> |
| 49 <loadproperties srcFile="project.properties" /> |
| 50 |
| 51 <!-- quick check on sdk.dir --> |
| 52 <fail |
| 53 message="sdk.dir is missing. Make sure to generate local.properties
using 'android update project' or to inject it through the ANDROID_HOME environm
ent variable." |
| 54 unless="sdk.dir" |
| 55 /> |
| 56 |
| 57 <!-- |
| 58 Import per project custom build rules if present at the root of the proj
ect. |
| 59 This is the place to put custom intermediary targets such as: |
| 60 -pre-build |
| 61 -pre-compile |
| 62 -post-compile (This is typically used for code obfuscation. |
| 63 Compiled code location: ${out.classes.absolute.dir} |
| 64 If this is not done in place, override ${out.dex.inpu
t.absolute.dir}) |
| 65 -post-package |
| 66 -post-build |
| 67 -pre-clean |
| 68 --> |
| 69 <import file="custom_rules.xml" optional="true" /> |
| 70 |
| 71 <!-- Import the actual build file. |
| 72 |
| 73 To customize existing targets, there are two options: |
| 74 - Customize only one target: |
| 75 - copy/paste the target into this file, *before* the |
| 76 <import> task. |
| 77 - customize it to your needs. |
| 78 - Customize the whole content of build.xml |
| 79 - copy/paste the content of the rules files (minus the top node) |
| 80 into this file, replacing the <import> task. |
| 81 - customize to your needs. |
| 82 |
| 83 *********************** |
| 84 ****** IMPORTANT ****** |
| 85 *********************** |
| 86 In all cases you must update the value of version-tag below to read 'cu
stom' instead of an integer, |
| 87 in order to avoid having your file be overridden by tools such as "andr
oid update project" |
| 88 --> |
| 89 <!-- version-tag: 1 --> |
| 90 <import file="${sdk.dir}/tools/ant/build.xml" /> |
| 91 |
| 92 </project> |
OLD | NEW |