Mirror of retrofit, Type-safe HTTP client for Android and Java by Square, Inc.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

build.xml 3.2KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <project name="test_app" default="help">
  3. <target name="-pre-build">
  4. <mkdir dir="libs"/>
  5. <!-- Copy native library. -->
  6. <copy todir="libs/armeabi">
  7. <fileset dir="../libs/armeabi"/>
  8. </copy>
  9. <!-- Copy Retrofit's Java library. -->
  10. <copy todir="libs">
  11. <fileset dir="../../../build" includes="retrofit-io*.jar"
  12. excludes="*src*"/>
  13. </copy>
  14. </target>
  15. <!-- The local.properties file is created and updated by the 'android'
  16. tool.
  17. It contains the path to the SDK. It should *NOT* be checked into
  18. Version Control Systems. -->
  19. <property file="local.properties" />
  20. <!-- The build.properties file can be created by you and is never touched
  21. by the 'android' tool. This is the place to change some of the
  22. default property values used by the Ant rules.
  23. Here are some properties you may want to change/update:
  24. source.dir
  25. The name of the source directory. Default is 'src'.
  26. out.dir
  27. The name of the output directory. Default is 'bin'.
  28. Properties related to the SDK location or the project target should
  29. be updated using the 'android' tool with the 'update' action.
  30. This file is an integral part of the build system for your
  31. application and should be checked into Version Control Systems.
  32. -->
  33. <property file="build.properties" />
  34. <!-- The default.properties file is created and updated by the 'android'
  35. tool, as well as ADT.
  36. This file is an integral part of the build system for your
  37. application and should be checked into Version Control Systems. -->
  38. <property file="default.properties" />
  39. <!-- Required pre-setup import -->
  40. <import file="${sdk.dir}/tools/ant/pre_setup.xml" />
  41. <!-- extension targets. Uncomment the ones where you want to do custom work
  42. in between standard targets -->
  43. <!--
  44. <target name="-pre-build">
  45. </target>
  46. <target name="-pre-compile">
  47. </target>
  48. [This is typically used for code obfuscation.
  49. Compiled code location: ${out.classes.absolute.dir}
  50. If this is not done in place, override ${out.dex.input.absolute.dir}]
  51. <target name="-post-compile">
  52. </target>
  53. -->
  54. <!-- Execute the Android Setup task that will setup some properties
  55. specific to the target, and import the build rules files.
  56. The rules file is imported from
  57. <SDK>/tools/ant/
  58. Depending on the project type it can be either:
  59. - main_rules.xml
  60. - lib_rules.xml
  61. - test_rules.xml
  62. To customize existing targets, there are two options:
  63. - Customize only one target:
  64. - copy/paste the target into this file, *before* the
  65. <setup> task.
  66. - customize it to your needs.
  67. - Customize the whole script.
  68. - copy/paste the content of the rules files (minus the top node)
  69. into this file, *after* the <setup> task
  70. - disable the import of the rules by changing the setup task
  71. below to <setup import="false" />.
  72. - customize to your needs.
  73. -->
  74. <setup />
  75. </project>