Brian Jones wrote:
> You shouldn't have to copy the files. Compiling them with the
> appropriate -d ${builddir}/lib should still work, it was working
> before I think.
I had to copy the files because the dependency generation was wrong.
> I've not fixed this I think. Are you using 2.0.2?
Heh. This might be the core of my problems. I have JavaDeps 1.0.4, which I
downloaded via the link on the gnu.org page. Where is the latest and
greatest program living?
> > As for the fully qualified problem, I just made manual modifications to the
> > classes I was having problems with (which was only a couple).
>
> I did fix this for 2.0.1 with a small patch. Here it is. I don't
> know if Steve added this to 2.0.2, but I don't think so.
Once I upgrade to 2.0.2, I'll look at applying the patch.
> > -- I upgraded us to the latest libtool which supposedly has the interlibrary
> > support.
>
> Yeah, but I don't know what needs to be done with it so I can't do
> much with this.
I'll be investigating this.
> I still want to try out jikes, because it also claims to generate
> dependency files capable of compiling java correctly. Assuming it
> works, it probably works better than JavaDeps. Anyone else wanna try
> it? Given they intend to make the license more open source, or indeed
> open source, would this be okay?
There are a couple of problems with the existing Jikes license, but I think
IBM intends to fix them. JavaDeps seems to be working now, though, so we are
under no pressure to change things.
Now I just need my Japhar integration ... I'm not going home for Christmas,
so my vacation will be a hacking marathon.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
