[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Running under windows

can we use Ant?


On Mon, 8 May 2000, Brian Weaver wrote:

> Peter,
> 
> 	Part of the problem with compiling Ozone on the Win32 platform is that the
> majority of the ozone developers are using Linux/Unix. The great command
> line tools that exist in real operating systems (i.e. unix :) don't by
> default come with the Win32 platform.
> 
> 	I recently went through the effort to compile the 0.4 release of ozone on a
> Windows NT 4.0 SP5 machine. First I would go to the cygwin site and download
> a copy of the Unix tools for windows. This will give you make, find, grep,
> and the other command line tools that Unix users just cannot do without.
> Next I would brace for a very difficult time of trial and error in the build
> process.
> 
> Here are some of the problems I encountered:
> 
> 1) Once I got a working set of build scripts, the first pass almost always
> failed. I believe, though I have not traced down, that there are some
> interdependencies that the java compiler could not figure out during the
> first compile. If I did not perform a 'make clean' right after the failed
> build and just type 'make' again and it would build without error.
> 
> 2) Add the 'bin' directory to your path before doing the build process. The
> build scripts need access to opp.bat, ojvm.bat, and others.
> 
> 3) I would encourage you to setup your own classpath to the .jar files in
> the ozone/bin directory. Also, include the root ozone directory in your
> classpath environment. After doing that edit the ozoneEnv.bat file and
> remark out the 'set CLASSPATH=..." statement. The problem with the
> ozoneEnv.bat file is that it would continually add the same jar files to the
> environment each time it was called. For some reason it cause the jdk1.2.2 I
> downloaded from Sun to barf. Unlike Linux/Unix I don't know how to check the
> classpath for the existence of a path or jar before adding it. Don't forget
> the classpath on Win32 is semicolon(;) separated unlike the Unix equilivent
> that is colon(:) separated.
> 
> 4) Don't forget to set OZONE_HOME, OZONE_JVM, and OZONE_JAVAC. Also, if you
> don't have jikes you might want to look through all the Makefiles & .bat
> files to make sure that it is not explicitly called. I can remember at least
> one instance where jikes was called instead of %OZONE_JAVAC% (or
> $OZONE_JAVAC for the Unix guys).
> 
> 5) Just remembered this. At least to makefiles had rules to the equilivant
> of "cd ../../../..; opp [more args]". On Unix the semicolon(;) would be a
> command separator. In make each line of a target rule is executed in it's
> own shell. The above command when passed to the shell will change
> directories up four levels and then run the opp command with it's arguments.
> On the Win32 platform this fails horribly! With the Cygwin tools I attempted
> to set the SHELL environment to '/bin/bash' to run the borne again shell as
> the command interpreter. We the cygwin make passes the command.com form of
> arguments.... "/c" instead of the Unix "-c" to make the shell execute the
> next command string.
> 
> Bash just did not like this one bit. So I ended up making a shell/bat file
> that took the arguments from the command and replaced the '/c' with '-c'.
> See the attached mbash.sh file.
> 
> That's all I can remember for now. Oh, one last thing.... If you want the
> java compiler to add debugging info (-g on javac) then you will need to set
> OZONE_JAVAC="javac -g" and edit the opp.bat file replacing %OZONE_JAVAC%
> with 'javac'. You will not be able to compile the *_Impl.java generated
> files with the -g option unless you hack the OPP.java file and recompile.
> Alternately you could use the -ks option with opp to keep the source and
> then hand compile it with the -g option from the command line.
> 
> I'm sure the Unix support for Ozone in the build process is infinitely
> better (just like Unix :) when compared to the Win32 platform, but a little
> pain for windows users until 1.0 isn't something to get bent out of shape on
> in my opinion. Falko has ask me to send him my changes to the build
> process..... Falko, there more or less outlined here. If you need more
> information or just want me to send you a tarball of the files as is just
> let me know. I'm currently using some spare brain cycles while being bored
> to death 37,000 ft above the ground. If you have any other question just
> send and e-mail.
> 
> 	Best of luck
> 
> 	Weave
> 	mailto:weave@opennms.org
> 
> 
> 
> -----Original Message-----
> From: Peter Newell [mailto:ppnewell@bellsouth.net]
> Sent: Saturday, May 06, 2000 1:43 AM
> To: Ozone Users
> Subject: Running under windows
> 
> 
> I downloaded ozone and got the server and admin running but when trying to
> run
> ojvm local under simple and others ojvm isn't understood there is a ojvm
> file in the bin, not sure if its a jar or what but I can't get it to run.
> 
> Any ideas?
> 
> Thanks,
> 
> Peter
>