[Kde-java] Packaging an application

[Richard Dale]

On Monday 01 April 2002 4:51 pm, Werner Punz wrote:
> Am Mon, 2002-04-01 um 17.43 schrieb Richard Dale:
> > On Sunday 31 March 2002 8:57 pm, George Russell wrote:
> > > How do I conviently package up a KDEJava application for end users?
> > > Any ideas?
> >
> > kdoc is a perl application rather than C++, but it uses 'configure.in'
> > and 'Makefile.in' to build and install, I adapted the same configure
> > files to install kalyptus bindings utility. The gilt install could put a
> > shell script with 'java <app path>/KSimpleBrowser' in the kde bin
> > directory, which would start the app in the apps/share directory.
> >
> > eg /opt/kde3/bin/gilt.sh sets up a classpath including
> > /opt/kde3/apps/share/gilt/gilt.jar and calls 'java KSimpleBrowser'
> >
> > I don't know how it works - a lot of the automake/autoconf stuff seems
> > 'black magic' to me. But I've attached the kalyptus Makefile.in and
> > configure.in - I think we need a standard install script like that for
> > java apps, so that people can just './configure ; make ; make install' as
> > usual.
> >
> > > Does anyone want to test my Etext reader?
> > > http://dogma.freebsd-uk.eu.org/~grrussel
> >
> > Looks pretty neat! I'm still rebuilding my system after a gcc/gcj 3.1
> > test, I'll try it out as soon as I can..
> >
> > I like the line 'All below this line is obsolete' refering to the
> > previous Swing version. How do you think the code compares?
> >
> > -- Richard
>
> Mhh Richard, have you looked at jakarta ant, this would be a great tool
> to do such stuff as make, packaging etc...
>
> Also there are several java based graphical installers which could be
> used (like JEdit uses) this simplifies installing for end users
> tremendously. I think the installer route could be the way to go in the
> long term. At least this is java, once the user has a JDK1.2+ up and
> running the rest could be handled by the installer.
> A simple jar distribution without a make would also be a good way. Jar +
> a readme on how to start it java -jar filename.jar would be an ok way to
> distribute binaries, as well as webstart could be thought as well.
With KDE you could build an .rpm, and then install with KPackage if the user 
prefers a graphic install. The other installers might be useful for 
installing Qt-only java programs - they would need to work on Windows too.

-- Richard