building cacao as an additional VM

[Mark Wielaard]

Hi Matthias,

On Tue, 2009-03-03 at 18:34 +0100, Matthias Klose wrote:
> Triggered by archive administrators and security people who don't want to care
> about two copies of the OpenJDK code in a distribution, I tried to build cacao
> as additional VM in the same source package and avoiding separate builds.

This is really convenient. Thanks!

> The cacao bits are installed in <top>/jre/lib/<arch>/cacao, cacao is configured
> like for the cacao build in IcedTea, the cacao-alternate-vm patch replaces the
> icedtea-cacao patch, cacao-jni-version needs applied to the cacao sources.
> The file jvm.cfg.in needs an additional line '-cacao KNOWN'.

You are introducing a new JNI_VERSION, is that really necessary? Could
you use jvmpath or the result of CheckJVMType () to select whether to
run in an new thread or not?

> Doing the same with Zero and with Shark? Didn't check yet, but maybe this would
> need a copy of openjdk/hotspot to openjdk/zero, so that patches are applied for
> the latter only.

Having the same for zero would indeed be pretty cool. Then you can
easily compare the same build between -client/-server/-cacao/-zero. I
haven't looked yet how much work that would be.

> There is no configure/make stuff for IcedTea yet; I'm currently assembling this
> directly in the packaging.
> 
> Ok to checkin these patches (without applying them)?

I would like to see configure stuff to enable this. That makes it easier
for everybody to compile and test it.

Cheers,

Mark