mobile/android/geckoview_library/build.xml

Wed, 31 Dec 2014 07:22:50 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Wed, 31 Dec 2014 07:22:50 +0100
branch
TOR_BUG_3246
changeset 4
fc2d59ddac77
permissions
-rw-r--r--

Correct previous dual key logic pending first delivery installment.

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

mercurial