> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Brian Jones
>
>
> "John Keiser" <[EMAIL PROTECTED]> writes:
>
> > We really need somehow to deal with this build thing. It will
> be a major
> > stumbling block for release. Without it, all we can do is
> release native
> > source and a classpath.zip kludged up from many different
> compilers. Oh,
> > and also a big ol' patch file for Japhar.
> >
> > As regards guavac, I have presented all the problems I specifically know
> > about to their mailing list and am waiting to see what comes up.
> >
>
> Hey guys,
>
> I was at the beach/wedding/concert this weekend so I didn't get to
> play with the build anymore. I'm planning to use JavaDeps to
> figure out dependencies for most class files. The two it has
> problems with I'll just have to do by hand, until that problem is
> fixed or we use something else. So I'll massage together the results
> to create something we can use and hopefully easily rebuild (except
> for two damn classes). :) If I'm going too slow on this, anyone feel
> free to step in.
>
> Brian
Hey, no problem at all. After trying to make classpath.zip, I know
personally what a nightmare it is. Curious: what are the problem files
JavaDeps can't parse, and why not? Maybe we can modify those two files to
work with JavaDeps.
Oh, and ... JavaDeps is written in Java, right? That means we'll have to do
the dependencies in the prebuild stage so that endusers don't have
chicken-egg problems. I'd hate to force them to download JDK just to
compile Classpath
Send me the completed Makefile when you're done. It'd be great to have a
full classes.zip.
--John Keiser
