emusonacid!

soulboy wrote:Hi there I thought I would let those that are interested know. I have refactored the directory structure, removed redundant copies of files, changed the pcmsmdi build system to use a ms nmake compatible make file and finally I checked the code into svn.

The project is here
http://code.google.com/p/zoeos/

Svn is here
https://zoeos.googlecode.com/svn/trunk/

I also modified the code so that it compiles with java 6 and removed the licensing part. The native source compiles too, to do it I installed visual studio express version and used nmake and the vs compiler. The make files used for the static libraries will need some changes depending on your system paths.

Anyone can checkout the code but you have to have an account to check in changes , if anyone wants a an account just pm.

I tried creating an executable jar but when I tried to execute the created jar file it couldnt find the main class. Do I need to set the classpath even though I tried executing from the same directory as the executable jar ?

Cheers

soulboy wrote:Today I managed get the native pcmsmdi library to build on Linux (this was already available for OpenSMDI and easy to do by following the instructions). This means that it will almost certainly build on OSX but I don't have a Mac to try it out. Does anyone with software development knowledge have an OSX system to build the library ? Maybe ZoeOS can work on MacOS with little effort now. The main issue after building the library is getting the java xFunction library to call the native library.

soulboy wrote:Thanks, I guess the main thing needed than non programmers could do is write the help documents. The latest version has a reasonable layout but every section says "Full documentation will be available in the next release of ZoeOS (v1.21) on January 24th 2004".

soulboy wrote:Hey thanks graphics could be useful in the future. Right now what is needed is a Java programmer and a C programmer who can regularly dedicate a little time to the project.
Of course they could be the same person. If I have an idea for new logo etc I will get in touch.

Without the executable jar file, and the detail error message
available, it's difficult to guess what the issue is. It could be that
the main class was no defined, or the correct java package was not
included in the jar.

Basically, if there is any dependancy on extarnal jars, those jars
will need to be on the classpath. But I think this particular issue is
the executable jar was not packaged properly. Open/extracting the
content of the executable jar, and have a look inside may reveal the
problem. e.g.

- did you include the class files instead of the java source file?
- did you define the Main-Class attribute in META-INF?

It would be helpful if they have a quick start guide for building the
software, or better yet, an Ant script that will build the project.

arkieboy wrote:I'm not a Java developer - I don't do anything that doesn't have an X in it and work in a browser! But one of my colleagues a very good one...

He says...

Without the executable jar file, and the detail error message
available, it's difficult to guess what the issue is. It could be that
the main class was no defined, or the correct java package was not
included in the jar.

Basically, if there is any dependancy on extarnal jars, those jars
will need to be on the classpath. But I think this particular issue is
the executable jar was not packaged properly. Open/extracting the
content of the executable jar, and have a look inside may reveal the
problem. e.g.

- did you include the class files instead of the java source file?
- did you define the Main-Class attribute in META-INF?

It would be helpful if they have a quick start guide for building the
software, or better yet, an Ant script that will build the project.

Does this make any sense to you

Steve