Making jnode vm standalone

Submitted by Starlord on Thu, 02/19/2004 - 07:13.

JNode-Core

Hi,i have bugged Ewout since the first release about how to make jnodevm as standalone, but i forgot the steps to make it as Ewout mailed me...

there has been huge changes in native code since i last looked,so if someone could give step by step instructions todo this.

why i'm asking WHY to make vm as standalone build also, is that it speeds and helps development of vm side as no need to build disk images for it.

so what i least need is ELF object out,which i last time i got from NativeStream(changed?) but what changes i need to make asm(atleast boot code remove?) and someway to boot native code...

The need is shifting

Submitted by admin on Thu, 02/19/2004 - 10:52.

Hi,

As you mention correctly there have been a lot of changes, including in the build system. The build is now much more incremental, so are you sure you still need this?

Cross Compilation?

Submitted by Patrik Reali on Thu, 02/19/2004 - 19:47.

There is something that puzzles me in the build process: the bootimage creator prints some information on the CPU on which it is compiled (a P-III in fact), but I'm going to run JNode on a P-I. Is this a problem? Is there a way to crosscompile JNode for a different machine?

Pentium is default target

Submitted by admin on Thu, 02/19/2004 - 20:46.

You can adjust the target CPU by setting the "cpu" property to "pentium", "pentium2", "pentium3" or "pentium4".

E.g. build.bat -Dcpu=pentium3

To be honoust, this does not make any difference right now, because the compiler does not differentiate yet, but it can be used to compile to a specific target. Especially for the optimizing compilers instructions like CMOV are interesting.

Why have target processors?

Submitted by N8Dawg on Wed, 03/03/2004 - 09:41.

I thought the advantage of the VM is it compiles and optimizes java code to the target processor. Why is this a build setting of the VM? Cant the VM compile and optimize itself for the target processor while its running? If this is the case can't it autodetect the flavour of processor its running on using the CPUID instruction on x86 at least.