Incremental jdk development

[Sean Mullan]

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

On 5/25/10 4:32 PM, Mandy Chung wrote:
> In the jigsaw repo, the makefile to modularize the jdk
> (make/modules/Makefile) is not optimized and it will reinstall all jdk
> modules in a module library every time it is made. Some of us have our
> own script to update the module library rather than remaking
> make/modules/Makefile.
>
> I include such script in the jigsaw/jdk repo for the incremental jdk
> development as an interim solution:
> http://hg.openjdk.java.net/jigsaw/jigsaw/jdk/file/335e3289aba7/make/modules/update_module.sh
>
>
> For example, after you recompile classes in some directory,
> $ cd make/java/java ; make all
>
> you can use the script to update the module library:
> $ make/modules/update_module.sh jdk.boot
>
> Please refer to the script for different options. Hope this helps.
>
> Mandy
> [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2010-May/000960.html