|
|
Building TINI Binaries Once you have compiled Java classes from their source, they need to be converted to TINI's binary format before they can be used. Dallas provide two utilities for creating binaries - TINIConvertor and BuildDependancy. These are well documented in the files Building_Applications.txt and BuildDependency_README.txt included in the TINI distribution. Basically TINIConvertor is used to build the TINI binary and can be used directly if your program does not depend on any classes that are not included in the standard TINI API. Make sure that tini.jar from the TINI SDK is in your class path and then the syntax is: java TINIConvertor -f Again with tini.jar in the classpath, the syntax is: java BuildDependency -f Where dependency list is a colon seperated list of dependencies to include, e.g. OneWireContainer04;OneWireContainer21 Here are a few shell scripts to keep the typing to a minimum… However, a far better way of automating the build process of TINI applications is to use TiniAnt, which is an extention to Apache Ant the cross platform build tool. TiniAnt adds a new task type, 1-Wire Example Code The source for some sample servlets using the 1-Wire API to control and monitor several devices can be downloaded below. These work fine on TINI in conjunction with TINIHttpServer, but note that the code has not been optimised for TINI's JVM. They will also work on other platforms that support Java and 1-Wire such as a PC equipped with a DS9097U serial to 1-wire adapter and running a suitable servlet container such as Jakarta Tomcat. To build the servlets into TINIHttpServer, the build.properties file in the source distribution must be modified. Specifically, alter the servlet.src property to reflct the locations of the servlet source and the onewire.deps property to include any dependencies. I found it easier to alter onewire.deps to a colon separated list of dependencies rather than using THS_ALL ro THS_MIN as this gives more control as to what is compiled in.
|
Version 1.3 last modified by cjb on 24/04/2007 at 23:41
Document data
Attachments:
No attachments for this document



Comments: 0