Porting Hotspot to other platforms / OS'es

[Kelly O'Hair]

I see Andrew posted a reply...

In general, there is a basic build dependency of building the JDK on having
a previously built JDK, often called the BOOT JDK.

But for hotspot (a part of the JDK), the BOOT JDK dependency is a little
unusual.
The hotspot repository does need to compile up some Java source for the
Serviceability Agent, but that could be skipped if what you were after was
just a libjvm.so (just the native hotspot C++ shared library), or you could
compile up that java agent source on a different machine, a class file is a
class file, doesn't matter who creates it.

But to build libjvm.so, some of the JVM TI code (Tools Interface) needs
to be generated, and that is done with XML/XSLT, however that generation
should be able to be done on some other machine.

I don't have any easy recipes, but I know it's possible.

Maybe if you built hotspot on a known build machine, then deleted the
.o and .so files, and tried building on the unknown machine?

-kto

Michael Neuweiler wrote:
> Hi,
> 
> I wanted to start porting OpenJDK to Syllable on Intel32 but got stuck 
> with the chicken and egg problem of hotspot: "you need a running JDK to 
> build a new one".
> 
> What are your recommendations to start a port? Is cross-compiling the 
> only solution or are there other ways?
> I think I saw once that an XSLT is started with an already installed 
> JRE/JDK during the build process on my Linux machine. Is this the only 
> reason why a JRE has to be installed?
> 
> Any help would be greatly appreciated!
> 
> Regards,
>  Michael Neuweiler
>