Incremental jdk development

[Alan Bateman]

Sean Mullan wrote:
> When you do a build from the jigsaw/jdk/make directory, what do you 
> set your ALT_HOTSPOT properties to? I tried setting them to the 
> following:
>
> ALT_HOTSPOT_IMPORT_PATH = /home/mullan/hg/jigsaw/build/linux-i586
> ALT_HOTSPOT_CLIENT_PATH = 
> /home/mullan/hg/jigsaw/build/linux-i586/lib/i386/client
> ALT_HOTSPOT_SERVER_PATH = 
> /home/mullan/hg/jigsaw/build/linux-i586/lib/i386/server
>
> but I'm getting the following error:
>
> make[3]: Entering directory 
> `/home/mullan/hg/jigsaw/jdk/make/java/redist/sajdi'
> make[3]: *** No rule to make target 
> `/home/mullan/hg/jigsaw/build/linux-i586/jre/lib/i386/libsaproc.so', 
> needed by `../../../../build/linux-i586/lib/i386/libsaproc.so'.  Stop.
> make[3]: Leaving directory 
> `/home/mullan/hg/jigsaw/jdk/make/java/redist/sajdi'
> make[2]: *** [all] Error 1
> make[2]: Leaving directory `/home/mullan/hg/jigsaw/jdk/make/java/redist'
> make[1]: *** [all] Error 1
> make[1]: Leaving directory `/home/mullan/hg/jigsaw/jdk/make/java'
> make: *** [all] Error 1
>
> something is still expecting the old jre/lib directory structure ...
>
> Thanks,
> Sean
It might be easier to start with a build of the entire forest and then 
do your incremental builds in the jdk repo with ALT_OUTPUTDIR set 
appropriately.

If you are doing partial builds like the above then you might be best to 
build the "all_product" target so that you have the complete export 
tree. That way you just need to set ALT_HOTSPOT_IMPORT_PATH (to  
build/linux-i586/export-linux-i586 in your case) -- ie: no need to set 
the ALT_HOTSPOT_{CLIENT,SERVER}_PATH variables.

-Alan.