build.xml Example File

 <?xml version="1.0" encoding="UTF-8"?>
 <project name="SimpleGame" default="help">

          It contains the path to the SDK. It should *NOT* be checked into
          Version Control Systems. -->
     <property file="" />

          'android' tool to add properties to it.
          This is the place to change some Ant specific build properties.
          Here are some properties you may want to change/update:

              The name of the source directory. Default is 'src'.
              The name of the output directory. Default is 'bin'.

          For other overridable properties, look at the beginning of the rules
          files in the SDK, at tools/ant/build.xml

          Properties related to the SDK location or the project target should
          be updated using the 'android' tool with the 'update' action.

          This file is an integral part of the build system for your
          application and should be checked into Version Control Systems.

     <property file="" />

          get it from the ANDROID_HOME env var.
          This must be done before we load since
          the proguard config can use sdk.dir -->
     <property environment="env" />
     <condition property="sdk.dir" value="${env.ANDROID_HOME}">
         <isset property="env.ANDROID_HOME" />

          tool, as well as ADT.

          This contains project specific properties such as project target, and library
          dependencies. Lower level build properties are stored in
          (or in .classpath for Eclipse projects).

          This file is an integral part of the build system for your
          application and should be checked into Version Control Systems. -->
     <loadproperties srcFile="" />

             message="sdk.dir is missing. Make sure to generate using 'android update project' or to inject it through the ANDROID_HOME environment variable."

         Import per project custom build rules if present at the root of the project.
         This is the place to put custom intermediary targets such as:
             -post-compile (This is typically used for code obfuscation.
                            Compiled code location: ${out.classes.absolute.dir}
                            If this is not done in place, override ${out.dex.input.absolute.dir})
     <import file="custom_rules.xml" optional="true" />

          To customize existing targets, there are two options:
          - Customize only one target:
              - copy/paste the target into this file, *before* the
                <import> task.
              - customize it to your needs.
          - Customize the whole content of build.xml
              - copy/paste the content of the rules files (minus the top node)
                into this file, replacing the <import> task.
              - customize to your needs.

          ****** IMPORTANT ******
          In all cases you must update the value of version-tag below to read 'custom' instead of an integer,
          in order to avoid having your file be overridden by tools such as "android update project"
     <import file="${sdk.dir}/tools/ant/build.xml" />


Voted #1 for:

  • Easiest to learn
  • Most time saving
  • Best support

Develop Cross-Platform Apps and Games 50% Faster!

  • Voted the best supported, most time-saving and easiest to learn cross-platform development tool
  • Based on the Qt framework, with native performance and appearance on all platforms including iOS and Android
  • Offers a variety of plugins to monetize, analyze and engage users
create apps
create games
cross platform
native performance
3rd party services
game network
level editor
easiest to learn
biggest time saving
best support