From: Godmar Back (gback@cs.utah.edu)
Date: Fri Dec 18 1998 - 18:36:42 EST
It's an issue I don't like to bring up cause it has to do with the build
environment.
1. On one hand, we have decided to minimize the number of "derived-files"
in the source tree, and to build as many of them on the fly as possible.
So for instance, we're now building java_lang_Cloneable on the fly,
but we are planning on building java_lang_Thread* and probably many of
the files in libraries/clib/*/*.h as well. And I think this is good.
2. On the other hand, as Alexandre pointed out in a previous mail,
kaffeh is part of the install target.
This scheme breaks down in the case of cross-compilation.
1. requires that kaffeh run on the build-platform, but create
header files that are valid for the target-platform.
2. requires that kaffeh run on the target-platform, but create
header files that are valid for the target-platform.
So, it seems that we either:
+ don't install kaffeh on the target platform. That seems bad.
+ switch to not generating derived files on the build platform.
That seems bad too.
+ build two versions of kaffeh. One that is compiled with the
compiler of the build platform which runs on the build-platform
and create the header files for the compilation of the VM,
and another one that runs on the target platform. The former
is kept in the build tree, the latter is installed.
I think the last one is the only viable alternative.
Another item on the TODO list...
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:23 EDT