Fooling around on my own with JavaDeps -- the problem that was snagging me
was really with in javac, not JavaDeps. If you're not compiling into the
same directory that your sources are in (i.e. there's a "-d" flag in the
javac line), your target directory has to be in the classpath or javac
will recompile all related files, royally screwing the timestamps and
making you have to recompile ad infinitum.
I got around this by setting
JAVACOMPILE = javac -d ../lib -classpath ../lib:${CLASSPATH}
in the Makefile.
(so it reads the rest of the classpath setting from the environment
variable).
Don't know if this helps for this project, but a heads up for those using
it elsewhere.
Wes
Brian Jones wrote:
> Update on JavaDeps. I've really hacked it. Added a few lines which
> removed my problem and I hope didn't cause any others. Found a new
> problem which really sucks. No dependencies are being made for
> classes already in your classpath at the time you use jdeps, or at
> least so it seems. I'll see if I can find where this is happening and
> stop it. And you have to know that after I got a good clean Makefile
> I was not happy to realize this last thing.
>
> Brian
