new build "Cheat sheet" question.

[Kelly O'Hair]

On Apr 12, 2012, at 1:47 PM, Mike Duigou wrote:

> 
> On Apr 12 2012, at 12:51 , Jonathan Gibbons wrote:
> 
>> In particular, it would be good to have a VERY PROMINENT section about how you suggest that JDK developers use the new build system as part of their daily activities, which typically do not involve using a full forest.
> 
> This is pretty key. I've yet to meet two OpenJDK developers using the same daily development process. This is mostly an artifact that all of their process recipes are largely self created. Then people stick with what "works" and introduce process change only when their current process stops working. Maintaining (which means updating them occasionally) a set of recipes that reflect suggested usage as part of the build documentation would be very useful.

I did a full jdk build (all openjdk repos including hotspot) on an Ubuntu 12.04 X64 system in my office,
a 3+ year old PC, nothing horribly special.  It took 10mins. A second 'make' completed in less than 10 seconds.
No import jdk was necessary, but I did need a jdk7 for the boot jdk, and used the openjdk-7-jdk package of 12.04.

So it's possible, if we have incremental builds working right, that the art of having to 'cd into some deep make directory'
and run 'make clean all'  isn't a style that makes any sense with the new build infrastructure.

Granted, I don't know if that 10min build will be true for Windows, Solaris, and all types of builds.
But nobody in their right mind would develop in Windows, at Oracle, with McAfee, and constant Updates,   would they?  Oh crap, JPRT does... :^(

-kto