From: D-Man <ds...@ri...> - 2001-03-08 15:08:07
|
On Thu, Mar 08, 2001 at 08:18:37AM -0600, William Dozier wrote: | My first guess at the easiest way to distribute this code was to use jythonc | to build a single jar that would hold all the Jython classes. That way the | users would only have to install a jre and Swing. However, I have not had I think that this would be the easiest way. | any success in getting jythonc (I get a very long list of compiler errors) | to complete this task and the documentation for it seems to be useful more | as a reference for experienced users than a tutorial for new ones. It would | be helpful to me if someone would post a detailed how-to for the complete | task of using jythonc to prepare a jar suitable for distribution to users | that will not have Jython installed. Hmm, when I tried jythonc I had no trouble at all. I simply gave it the --jar and --deep (or --all) options and it built a jar file containing java bytecodes for my python source and the jython interpreter bundled together. Could you post the errors you are getting? | If I don't use jythonc, what other ways do you all find to work well? Can I | take the .class files built by Jython and use another tool (like | ClassWrangler on the Mac) to build a jar that I could distribute with | jython.jar? AFAIK jythonc merely takes the .class files it outputs and the .class files necessary from the jython.jar file and puts it into a new jar file. (Ok, a simplification since it first generates Java source and also figures out dependencies) If you want to do that by hand, the 'jar' part of the JDK should be able to handle it. jar is run very similarly to tar except it produces a .jar file instead of a .tar file. HTH, -D |