-
Enhancement
-
Resolution: Fixed
-
P4
-
5.0
-
b42
-
generic
-
generic
Each time the j2se workspace is built from the make directory,
all the hotspot files like libjvm.so are re-copied from
ALT_HOTSPOT_SERVER_PATH etc.. into the j2se workspace.
This should be done lazily.
`make' is the perfect tool to implement the laziness.
In makefile pseudocode:
${WORKING_BUILD}/libjvm.so : ${PROMOTED_BUILD}/libjvm.so
${CP} -p $< $@
If a new promotion happens, the local libjvm.so will be
correctly updated.
###@###.### 2003-08-22
Actually, the above isn't quite correct. The libjvm.so needs to be
copied whenever the file changes in any way. We really want
something like rsync, that can efficiently copy files, and
will avoid copies if the timestamp and file sizes match.
But we can't rely on the rsync program itself being available,
without adding an added dependency to the build process.
###@###.### 2003-08-29
all the hotspot files like libjvm.so are re-copied from
ALT_HOTSPOT_SERVER_PATH etc.. into the j2se workspace.
This should be done lazily.
`make' is the perfect tool to implement the laziness.
In makefile pseudocode:
${WORKING_BUILD}/libjvm.so : ${PROMOTED_BUILD}/libjvm.so
${CP} -p $< $@
If a new promotion happens, the local libjvm.so will be
correctly updated.
###@###.### 2003-08-22
Actually, the above isn't quite correct. The libjvm.so needs to be
copied whenever the file changes in any way. We really want
something like rsync, that can efficiently copy files, and
will avoid copies if the timestamp and file sizes match.
But we can't rely on the rsync program itself being available,
without adding an added dependency to the build process.
###@###.### 2003-08-29