Getting started with jdb support - getting the main prog from gideonprj

[Richard Dale]

I think KDE should have a global mechanism of setting up class paths, or assume
that classes can be found in a standard place. I haven't looked into how you
might start a java application from a KDE menu yet, but obviously that's quite
important for delivering applications useful to end users (cf Swing).

JAVAROOT is intended to be a build time thing, rather than a run time thing,
as far as I know.

-- Richard


On Thu, 19 Apr 2001, you wrote:
> On Thursday 19 April 2001 18:57, Richard Dale wrote:
> > On Thu, 19 Apr 2001, you wrote:
> > > Without relative path? It surprises me that it works, as you probably
> > > have the .class file in a subdirectory?
> >
> > Yes, you're right - it didn't have 'src' in the path. Should it - is that a
> > bug - can we assume that an automake project will always have a src
> > directory? You can't put 'src/ScribbleWindow' in the gideonprj file, it
> > didn't get parsed. In jdbcontroller, I stripped off the path and and just
> > ran a 'jdb ScribbleWindow' command, relying on the $CLASSPATH to be set up
> > for the 'src' directory. I think it should strip off the directory path and
> > add that to the contents of $CLASSPATH, then pass that as a '-classpath'
> > parameter to jdb.
> 
> That's what I am currently doing with my hard codes filenames and paths and I 
> think project options should offer a way to set both the "normal" classpath 
> (can initially be taken from $CLASSPATH) and the base directory of source 
> files (where generated classfiles will probably go to) or something like 
> JAVAROOT.

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«