|
1 | 1 | <?xml version="1.0" encoding="UTF-8"?>
|
2 |
| -<project name="main" default="help"> |
| 2 | +<project name="sharethis_mobile" default="help"> |
3 | 3 |
|
4 | 4 | <!-- The local.properties file is created and updated by the 'android' tool.
|
5 | 5 | It contains the path to the SDK. It should *NOT* be checked into
|
6 | 6 | Version Control Systems. -->
|
7 |
| - <loadproperties srcFile="local.properties" /> |
| 7 | + <property file="local.properties"/> |
8 | 8 |
|
9 | 9 | <!-- The ant.properties file can be created by you. It is only edited by the
|
10 | 10 | 'android' tool to add properties to it.
|
|
26 | 26 | application and should be checked into Version Control Systems.
|
27 | 27 |
|
28 | 28 | -->
|
29 |
| - <property file="ant.properties" /> |
| 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> |
30 | 39 |
|
31 | 40 | <!-- The project.properties file is created and updated by the 'android'
|
32 | 41 | tool, as well as ADT.
|
|
37 | 46 |
|
38 | 47 | This file is an integral part of the build system for your
|
39 | 48 | application and should be checked into Version Control Systems. -->
|
40 |
| - <loadproperties srcFile="project.properties" /> |
| 49 | + <loadproperties srcFile="project.properties"/> |
41 | 50 |
|
42 | 51 | <!-- quick check on sdk.dir -->
|
43 | 52 | <fail
|
44 |
| - message="sdk.dir is missing. Make sure to generate local.properties using 'android update project'" |
| 53 | + 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." |
45 | 54 | unless="sdk.dir"
|
46 |
| - /> |
47 |
| - |
48 |
| - |
49 |
| -<!-- extension targets. Uncomment the ones where you want to do custom work |
50 |
| - in between standard targets --> |
51 |
| -<!-- |
52 |
| - <target name="-pre-build"> |
53 |
| - </target> |
54 |
| - <target name="-pre-compile"> |
55 |
| - </target> |
56 |
| -
|
57 |
| - /* This is typically used for code obfuscation. |
58 |
| - Compiled code location: ${out.classes.absolute.dir} |
59 |
| - If this is not done in place, override ${out.dex.input.absolute.dir} */ |
60 |
| - <target name="-post-compile"> |
61 |
| - </target> |
62 |
| ---> |
| 55 | + /> |
| 56 | + |
| 57 | + <!-- |
| 58 | + Import per project custom build rules if present at the root of the project. |
| 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.input.absolute.dir}) |
| 65 | + -post-package |
| 66 | + -post-build |
| 67 | + -pre-clean |
| 68 | + --> |
| 69 | + <import file="custom_rules.xml" optional="true"/> |
63 | 70 |
|
64 | 71 | <!-- Import the actual build file.
|
65 | 72 |
|
|
80 | 87 | in order to avoid having your file be overridden by tools such as "android update project"
|
81 | 88 | -->
|
82 | 89 | <!-- version-tag: 1 -->
|
83 |
| - <import file="${sdk.dir}/tools/ant/build.xml" /> |
| 90 | + <import file="${sdk.dir}/tools/ant/build.xml"/> |
84 | 91 |
|
85 | 92 | </project>
|
0 commit comments