Permalink
Newer
100644
110 lines (81 sloc)
4.91 KB
|
||
| 1 | <?xml version="1.0" encoding="UTF-8" standalone="no"?><project basedir="." default="help" name="PowerScaling@SunSPOT"> | |
| 2 | ||
| 3 | <!-- You may freely edit this file. See commented blocks below for --> | |
| 4 | <!-- some examples of how to customize the build. --> | |
| 5 | ||
| 6 | <!-- | |
| 7 | ||
| 8 | The master build file lives at: ${sunspot.home}/build.xml. | |
| 9 | ||
| 10 | If you do not have a Sun SPOT properties file for some reason, | |
| 11 | then you can set the sunspot.home property manually. | |
| 12 | ||
| 13 | <property name="sunspot.home" value="/opt/sunspot"/> | |
| 14 | ||
| 15 | The behavior of the build is also controled through properties. | |
| 16 | For example, to use a different source directory, you can set | |
| 17 | the property 'src.dir'. | |
| 18 | ||
| 19 | <property name="src.dir" value="mysrc"/> | |
| 20 | ||
| 21 | For a complete listing of properties that are used, and their | |
| 22 | explanations, see the file ${sunspot.home}/default.properties. | |
| 23 | ||
| 24 | --> | |
| 25 | ||
| 26 | <property name="user.properties.file" value="build.properties"/> | |
| 27 | <property file="${user.home}/.sunspot.properties"/> | |
| 28 | <import file="${sunspot.home}/build.xml"/> | |
| 29 | ||
| 30 | <!-- | |
| 31 | ||
| 32 | This file imports the master build file for compiling and deploying sunspot | |
| 33 | applications. This file provides hooks for the user build file, so that | |
| 34 | you can accomplish almost anything without having to rewrite any of the | |
| 35 | build procedures. However, if need be, you can just look at the imported | |
| 36 | build file to determine how exactly any step is accomplished. | |
| 37 | ||
| 38 | Of course, another useful way to find out exactly what is happening is to | |
| 39 | run the targets listed below with ant's 'verbose' flag (ant -v). This will | |
| 40 | display exactly what is happening at each step. | |
| 41 | ||
| 42 | Some important targets that are defined within the master build file are: | |
| 43 | (Do "ant help" to see the full list.) | |
| 44 | ||
| 45 | init: initialize and check all properties | |
| 46 | help: display useful a help message | |
| 47 | environment displays information about setting up your environment | |
| 48 | sdk-info displays information about the current SDK installation | |
| 49 | find-spots locate USB ports where SPOTs are connected | |
| 50 | info displays information about the configuration of a SPOT | |
| 51 | slots displays a list of the applications deployed on the SPOT | |
| 52 | ||
| 53 | clean: delete all compiled/generated files | |
| 54 | compile: compiles java source files to classes | |
| 55 | jar-app Create a jar for this application | |
| 56 | deploy deploy the application to a SPOT as an IMlet | |
| 57 | jar-deploy deploy an IMlet jar | |
| 58 | run connect to a device and watch the application | |
| 59 | debug-run configure the SPOT ro run the debug agent and then start the debug proxy | |
| 60 | debug-proxy-run start the proxy for the high-level debugger | |
| 61 | ||
| 62 | Some useful command line properties: | |
| 63 | ||
| 64 | -Dbasestation.addr=1234 set the address of the basestation | |
| 65 | -DremoteId=1234 set the target for remote run/deploy/debug-proxy-run | |
| 66 | -Dsquawk.startup.class=com.example.MyStartUp | |
| 67 | set an alternative startup class name | |
| 68 | -Dspotport=COM2 set the port name for communicating with the SPOT | |
| 69 | -Djar.file=example.jar set the jar file for jar-app, jar-deploy and make-host-jar | |
| 70 | -Dmidlet=2 select a midlet to run for selectapplication | |
| 71 | or deploy targets (defaults to 1) | |
| 72 | -Dutility.jars=utils.jar a classpath separator delimited list of jars to be | |
| 73 | included with the application | |
| 74 | ||
| 75 | There exist several targets which are by default empty and which can be | |
| 76 | used for execution of your tasks. These targets are usually executed | |
| 77 | before and after some main targets. They are defined as follows: | |
| 78 | ||
| 79 | For each target above (except help), | |
| 80 | ||
| 81 | -pre-<target>: called before the target | |
| 82 | -post-<target>: called after the target | |
| 83 | ||
| 84 | For example, inserting an echo statement after compilation could look like this: | |
| 85 | ||
| 86 | <target name="-post-compile"> | |
| 87 | <echo>Compile finished!</echo> | |
| 88 | </target> | |
| 89 | ||
| 90 | For more information on using ant, see http://ant.apache.org. | |
| 91 | ||
| 92 | --> | |
| 93 | ||
| 94 | <!-- | |
| 95 | Below is an example target to create Javadoc for your project. | |
| 96 | ||
| 97 | Note: you must manually edit the packagenames argument with | |
| 98 | the packages that you wish to create Javadoc for. | |
| 99 | --> | |
| 100 | ||
| 101 | <target depends="init" name="javadoc"> | |
| 102 | <delete dir="doc"/> | |
| 103 | <mkdir dir="doc"/> | |
| 104 | <javadoc author="true" destdir="doc" doctitle="Cargo Monitoring Pilot. DEMANES Project (1.0)" packagenames="eu.artemis.demanes.impl.SunSPOT.*" sourcepath="src" windowtitle="Cargo Monitoring Pilot. DEMANES Project (1.0)"> | |
| 105 | <classpath path="${sunspot.classpath}:${sunspot.bootclasspath}"/> | |
| 106 | <header><![CDATA[<b>DEMANES Power Scaling -- SPOT-side<br>v1.0</b>]]></header> | |
| 107 | </javadoc> | |
| 108 | </target> | |
| 109 | ||
| 110 | </project> |