bernd at physik.hu-berlin.de
Tue Jun 5 09:00:52 UTC 2001
On Sun, 3 Jun 2001, Richard Dale wrote:
> > On Sat, 2 Jun 2001, Richard Dale wrote:
> > > I've found the _JAVA primary reasonably ok to use. The only problem with it
> > > that I would like to be able to solve, is to not install '.class' files when a
> > > '.jar' file is all that is wanted - it ends up installing both for me at the
> > > moment. I'm afraid I don't know anything about ant or jakarta, and I haven't
> > > used other Java IDEs to know how they might handle the project builds.
> > Well, I've just seen it mentioned in at least two different magazines as
> > a cross-platform solution for building java programs, so I thought it has
> > some relevance... I haven't read the articles though
> I am keen on KDE oriented Java development, rather than existing sorts of
> Java development, and I think automake/am_edit etc. is a pretty essential part
> of the (complicated) KDE build/install process. I would like to be able to build
> perfectly standard KDE apps or KParts, which just happen to contain Java
> resources for all or part of the application logic.
I don't want to divert you from your mission :-) For installing non-code
files, automake and KDE's acinclude.m4 have their merits of course.
> One restriction of the _JAVA primary is that you can only have one of them,
> unlike _SOURCES. I would describe automake Java support as 'feeble, but
> probably good enough'.
Okay, this restriction is also something to consider in the project
management. I'll have a look at that.
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel