>>>>> "EHusby" == EHusby <[EMAIL PROTECTED]> writes:
EHusby> I was recently working with JDK1.2 and have just installed
EHusby> JDK1.2.2. All my project files had the compiler defined as
EHusby> "c:/jdk1.2/bin/javac". This, obviously, has to be changed.
EHusby> Instead of putting the string "javac" in the project file,
EHusby> could I put a reference to a ELisp function that would
EHusby> return the correct string? I could see a function like:
EHusby> (defun jdk2 (a)
EHusby> (concat (getenv "JDK2") a))
EHusby> Where "JDK2" was an environment variable for the current
EHusby> JDK1.2 installation. Then in the project file replacing the
EHusby> entry for "javac" with (jdk2 "javac") or the equivalent.
Actually thinking about this a little bit more carefully,
couldnt you just get the shell to expand your jdk1.2 thing. Exactly
how you do this will depend on your shell but windows syntax would be
something like %JDK2%\bin\javac, or $JDK2\bin\javac in bash which you could
just stick straight inside the customization region.
Ive just given it a bash (bad pun) and got the following effects
cd d:/home/java/sources/test/
$PATH/bin/jikes -classpath "e:/jdk1.2/jre/lib/rt.jar;d:/home/java/packages" -d
d:/home/java/packages +E JBigLabel.java
/CYGNUS/CYGWIN-B20/H-I586-CYGWIN32/BIN/bash.exe:
.:/CYGNUS/CYGWIN-B20/H-I586-CYGWIN32/BIN:/d/HOME/BATS:/PERL/BIN:/windows:/windows/command/bin/jikes:
No such file or directory
Compilation exited abnormally with code 127 at Wed Jul 21 01:29:17
using my PATH env, which is clearly inappropriate but
demonstrates the point that the expansion is taking place as desired.
Phil
