From: Archie Cobbs (archie@whistle.com)
Date: Wed Sep 09 1998 - 21:01:04 EDT
Godmar Back writes:
> > I was wrong to suggest that kaffe should be re-built using the
> > version just installed... all building should be done using a fixed
> > set of tools (even kaffeh). Nothing that gets built should be
> > executed during the building process. Is that more consistent with
> > what you had in mind?
>
> I wouldn't be that dogmatic.
>
> a) If we build kaffeh first, use it create the derived headers from the
> provided Klasses.jar, that seems fine to me too.
> b) For the libraries, we first rely on the "fixed set of tools" you're
> referring to, except maybe kaffeh.
> c) After that, we try to use what we just built to compile the libraries
> again, just like gcc stage1 compiles gcc stage2.
>
> a) would occur in every build, b) only if you changed the .java files,
> c) only after b) if you want to test your changes more thoroughly.
So in summary...
- Normal builds will not regenerate any derived files (the way it is now)
- A "make derived-files" should:
- Use the pre-existing tools in the environment to compile the classes
- Use the kaffeh just built to generate header files (by reaching
into the appropriate object directory).
- To implement (c), you can "make install" as required so that the kaffe
and pizza you install overwrite your "pre-existing tools".
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:56:56 EDT