>>> "Schewe, Jon (MN65)" <[EMAIL PROTECTED]> 02-Nov-00
12:07:31 AM >>>
>Ahh, here's your problem, you need to learn to write prj.el
>files with everything setup using elisp variables.
I understand you could do it that way...
I prefer Paul's idea of a common project file and then everything
else creates instances... The common project file should be specified
by some global configuartion variable and thus could be set in .emacs
or site-lisp.
I'm carving up my JDE source as we speak.
Another reason for re-modelling the compile stuff occurred to me
since I started doing it - the JDE has a fixed understanding of what
compile options are taken by the compiler.
For example -bootclasspath is used as the switch for setting the
classpath of the classes that the compiler will use to run itself.
The problem with that is that not all compilers use the same
switches. The Kopi compiler (comes default with Kaffe) doesn't do it
that way for example.
One of the things my hook based system will be able to do it to use
generate a different compile command for different compilers.
I thought what I'd do is have a configuration option for compiler
which is a choice option, the choice will be:
- javac
- jikes
- make
- emacs-lisp function by name
The last option is designed to allow you to do custom compilations if
you have peculiar requirements or if you want to use an unusual
compiler.
Of course, this point about switches applies to a lot of other
commands in the JDE. When I'm using Kaffe I get very frustrated about
the use of some switches which Kaffe supports in functionality but not
by name.
Perhaps the same sort of "hook" system needs to be applied to these
other parts of the JDE.
Nic
