1 <?xml version="1.0" encoding="UTF-8"?>
3 * Copyright (C) 2012 OUYA, Inc.
5 * Licensed under the Apache License, Version 2.0 (the "License");
6 * you may not use this file except in compliance with the License.
7 * You may obtain a copy of the License at
9 * http://www.apache.org/licenses/LICENSE-2.0
11 * Unless required by applicable law or agreed to in writing, software
12 * distributed under the License is distributed on an "AS IS" BASIS,
13 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14 * See the License for the specific language governing permissions and
15 * limitations under the License.
17 <project name="game_sample" default="help">
19 <!-- The local.properties file is created and updated by the 'android' tool.
20 It contains the path to the SDK. It should *NOT* be checked into
21 Version Control Systems. -->
22 <property file="local.properties"/>
24 <!-- The ant.properties file can be created by you. It is only edited by the
25 'android' tool to add properties to it.
26 This is the place to change some Ant specific build properties.
27 Here are some properties you may want to change/update:
30 The name of the source directory. Default is 'src'.
32 The name of the output directory. Default is 'bin'.
34 For other overridable properties, look at the beginning of the rules
35 files in the SDK, at tools/ant/build.xml
37 Properties related to the SDK location or the project target should
38 be updated using the 'android' tool with the 'update' action.
40 This file is an integral part of the build system for your
41 application and should be checked into Version Control Systems.
44 <property file="ant.properties"/>
46 <!-- if sdk.dir was not set from one of the property file, then
47 get it from the ANDROID_HOME env var.
48 This must be done before we load project.properties since
49 the proguard config can use sdk.dir -->
50 <property environment="env"/>
51 <condition property="sdk.dir" value="${env.ANDROID_HOME}">
52 <isset property="env.ANDROID_HOME"/>
55 <!-- The project.properties file is created and updated by the 'android'
58 This contains project specific properties such as project target, and library
59 dependencies. Lower level build properties are stored in ant.properties
60 (or in .classpath for Eclipse projects).
62 This file is an integral part of the build system for your
63 application and should be checked into Version Control Systems. -->
64 <loadproperties srcFile="project.properties"/>
66 <!-- quick check on sdk.dir -->
68 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."
73 Import per project custom build rules if present at the root of the project.
74 This is the place to put custom intermediary targets such as:
77 -post-compile (This is typically used for code obfuscation.
78 Compiled code location: ${out.classes.absolute.dir}
79 If this is not done in place, override ${out.dex.input.absolute.dir})
84 <import file="custom_rules.xml" optional="true"/>
86 <!-- Import the actual build file.
88 To customize existing targets, there are two options:
89 - Customize only one target:
90 - copy/paste the target into this file, *before* the
92 - customize it to your needs.
93 - Customize the whole content of build.xml
94 - copy/paste the content of the rules files (minus the top node)
95 into this file, replacing the <import> task.
96 - customize to your needs.
98 ***********************
99 ****** IMPORTANT ******
100 ***********************
101 In all cases you must update the value of version-tag below to read 'custom' instead of an integer,
102 in order to avoid having your file be overridden by tools such as "android update project"
104 <!-- version-tag: 1 -->
105 <import file="${sdk.dir}/tools/ant/build.xml"/>