Why demo/sample before launchers?
weijun.wang at oracle.com
Mon Dec 6 03:46:44 UTC 2010
Thanks for the info.
If the new image is not used, does that mean there can be some kind of
dependency check in Makefiles for demo/sample? Currently these two are
always rebuilt entitely and occupies most of the time in doing an
increment jdk build.
On 12/06/2010 11:38 AM, Kelly O'Hair wrote:
> On Dec 5, 2010, at 5:12 PM, Weijun Wang wrote:
>> Hi Kelly
>> I noticed that in jdk build, demo and sample are before launchers. In
>> a jdk-only build, JDK_IMPORT_PATH's javac is used. Otherwise,
>> BOOTDIR's javac using javac.jar built from langtools is used. Why not
>> build launchers first and use the brand new javac to compile demo/sample?
> The goal was to try and completely build a jdk image without using that
> same image as part of the build process.
> That was why I pushed the launcher creations to the very end.
> It allows for cross compilation builds, where we can't necessarily run
> the jdk image being built.
> Granted, we obviously still need to make more adjustments for cross
> compile builds to work really well.
More information about the build-dev