| | 1 | <?xml version="1.0" encoding="UTF-8"?> |
| | 2 | <project name="MS2Debounce" 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 | <!-- The project.properties file is created and updated by the 'android' |
| | 32 | tool, as well as ADT. |
| | 33 | |
| | 34 | This contains project specific properties such as project target, and library |
| | 35 | dependencies. Lower level build properties are stored in ant.properties |
| | 36 | (or in .classpath for Eclipse projects). |
| | 37 | |
| | 38 | This file is an integral part of the build system for your |
| | 39 | application and should be checked into Version Control Systems. --> |
| | 40 | <loadproperties srcFile="project.properties" /> |
| | 41 | |
| | 42 | <!-- quick check on sdk.dir --> |
| | 43 | <fail |
| | 44 | message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through an env var" |
| | 45 | unless="sdk.dir" |
| | 46 | /> |
| | 47 | |
| | 48 | <!-- |
| | 49 | Import per project custom build rules if present at the root of the project. |
| | 50 | This is the place to put custom intermediary targets such as: |
| | 51 | -pre-build |
| | 52 | -pre-compile |
| | 53 | -post-compile (This is typically used for code obfuscation. |
| | 54 | Compiled code location: ${out.classes.absolute.dir} |
| | 55 | If this is not done in place, override ${out.dex.input.absolute.dir}) |
| | 56 | -post-package |
| | 57 | -post-build |
| | 58 | -pre-clean |
| | 59 | --> |
| | 60 | <import file="custom_rules.xml" optional="true" /> |
| | 61 | |
| | 62 | <!-- Import the actual build file. |
| | 63 | |
| | 64 | To customize existing targets, there are two options: |
| | 65 | - Customize only one target: |
| | 66 | - copy/paste the target into this file, *before* the |
| | 67 | <import> task. |
| | 68 | - customize it to your needs. |
| | 69 | - Customize the whole content of build.xml |
| | 70 | - copy/paste the content of the rules files (minus the top node) |
| | 71 | into this file, replacing the <import> task. |
| | 72 | - customize to your needs. |
| | 73 | |
| | 74 | *********************** |
| | 75 | ****** IMPORTANT ****** |
| | 76 | *********************** |
| | 77 | In all cases you must update the value of version-tag below to read 'custom' instead of an integer, |
| | 78 | in order to avoid having your file be overridden by tools such as "android update project" |
| | 79 | --> |
| | 80 | <!-- version-tag: 1 --> |
| | 81 | <import file="${sdk.dir}/tools/ant/build.xml" /> |
| | 82 | |
| | 83 | </project> |
projects / ms2-fixes / blame_incremental