Difference between revisions of "Using the Java Virtual Machine"
m (→Compiling Programs: Fixed grammatical errors.) |
m (Improved description of the JVM so that it doesn't sound like we expect the customer to be someone who doesn't have a CS or Engineering background.) |
||
Line 11: | Line 11: | ||
== JamVM == | == JamVM == | ||
− | A Java virtual machine (JVM) is the software that converts Java bytecode into a program that can run in the target system. Java mostly uses the just in time (JIT) compilation method which partially compiles the code | + | A Java virtual machine (JVM) is the software that converts Java bytecode into a program that can run in the target system. Java mostly uses the just in time (JIT) compilation method which partially compiles the java source code into java bytecode. The JVM on any target can compile the java bytecode into the machine code for the target architecture. The JIT method saves time by performing the parsing, lexical analysis, and source level optimization steps ahead of time, thus allowing the same bytecode to have the final translation into the bytecode for multiple separate platforms at the moment the program is executed on the target platform. The Java Virtual Machine that is included in the EMAC package is JamVM. JamVM is a small, open source virtual machine that conforms to the Java virtual machine specification version 2. |
== Compiling Programs == | == Compiling Programs == |
Revision as of 13:53, 7 May 2014
The Java Virtual Machine is an optional package and is not included by default in EMAC Linux builds. If you would like to include this package with your build, the custom package number is SL040-NPN-00140. To inquire about purchasing this package, please contact EMAC at info@emacinc.com.
JamVM
A Java virtual machine (JVM) is the software that converts Java bytecode into a program that can run in the target system. Java mostly uses the just in time (JIT) compilation method which partially compiles the java source code into java bytecode. The JVM on any target can compile the java bytecode into the machine code for the target architecture. The JIT method saves time by performing the parsing, lexical analysis, and source level optimization steps ahead of time, thus allowing the same bytecode to have the final translation into the bytecode for multiple separate platforms at the moment the program is executed on the target platform. The Java Virtual Machine that is included in the EMAC package is JamVM. JamVM is a small, open source virtual machine that conforms to the Java virtual machine specification version 2.
Compiling Programs
It is not currently possible to compile a Java program directly on an EMAC board. A development computer is needed to compile the program and send the bytecode to the board. The process of compiling a basic Java program is fairly simple; the command for compiling the file HelloWorld.java
is:
developer@ldc:~$ javac HelloWorld.java
The javac
command calls the Java compiler on the HelloWorld.java
source file and produces a file called HelloWorld.class
. The HelloWorld.class
file will be used to run the program.
NOTE: The name of the class in the Java source file must match the basename of the file (the filename without the .java extension). |
The resulting class file will need to be sent to the target board to be run. The easiest way to accomplish this is through scp
. Assuming the IP address 10.0.2.40
, the command is:
developer@ldc:~$ scp HelloWorld.class root@10.0.2.40:/root
Running Programs
Running a compiled Java program is accomplished by passing the class name to java. To run the HelloWorld program, use the following command with the HelloWorld.class
file in the current directory.
developer@ldc:~$ java HelloWorld
NOTE: The value passed to the java command is the name of a class, not a file name.. |
Included Examples
EMAC includes a few sample Java programs on the builds that include the JamVM package. The examples are located in the /home/user/Java-Examples
. Both the source files and class files are included on the board. If changes need to be made to a source file, the class file will need to be recompiled on a development computer and sent back to the target board.
The included examples are:
- BinaryConverter
- GameOfLife
- HelloWorld
- KeyboardReader
- PrimeNumbers