I downloaded the binary version and all I have to do is:
java -jar batik-squiggle.jar
If you are building from source, try:
./build.sh dist-tgz
This should give you the binary distribution.
hth,
-Sumeet
> -----Original Message-----
> From: John Griessen [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 19, 2003 3:32 PM
> To: [EMAIL PROTECTED]
> Subject: using squiggle, java classpath strategy
>
>
> Hi,
>
> I'm learning by doing, and have gone through the
> batik install from source process and run squiggle. It takes
> 37 seconds
> to start it each time that way...so I found the target list
> of build.sh
> and built dist-zip and got .jar files. I moved those to
> /usr/local/classes/batik-1.5
> and set the classpath to the dir some jar files are in and nothing.
>
> Then I read that that is normal classpath behavior.
>
> So, my question to you all is:
>
> Is it better to copy or move the generated classes directory
> tree contents to your basic
> /usr/local/classes directory so as to have shorter classpath=
> environment variables,
> or is it somehow preferable to have a long classpath=
> pointing to many of
> the .jar files generated? Each is going to have a compile
> step. Each is likely to require
> a copy from the build dir to the dirs on the classpath. Do
> you all prefer to just put the
> build dirs of code youare changing on your classpath? The
> tutorials on classpath say
> to avoid confusion and keep them short or use jwhich and such
> tools to sort out confusion...
>
> Thanks for any hints,
>
> JG
>
> --
> John Griessen Cibolo Design Austin Texas
> EE good at IR systems, power supplies, logic design, A2D D2A,
> digital amps,
> mechatronics, SiGe and CMOS layout, MEMS/mech/electronic/photonic
> modeling, charge pump PV/battery/fuel cell power converters,
> linux counter #249315
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
