Michael L Brereton
www.ewesoft.com
Eve Virtual Machine Runtimes:
Java 2 (or better) Runtime Environment.
Windows Desktop.
Windows Mobile Devices.
Linux Desktop.
Linux Nokia Mobile Devices.
For Developers:
Software
Development Kit (SDK)
Source
Code
This consists of the file eve.jar – which contains the entire Eve
library targeted for Java 2 virtual machines. To run an Eve application
packaged as a .eve file, use the command line:
java -cp eve.jar Eve <full_path_to_eve_file>
There is also the file evecl.jar – which contains the Eve library
without any GUI or graphics capabilities. This is useful for running command
line versions of Eve applications on embedded systems.
There is also the file evecl-gui.jar – which contains the Eve UI
library but which cannot bring up a user interface because it does not link to
any Java AWT or Swing libraries. (This particular version is only useful for
using Eve applications that have references to the eve.ui
library and need it to be present).
All of these .jar files can be downloaded from the link below:
Eve for Java 2 Runtime Environment
This version works on Windows XP/Vista/7. It has not been tested for
Windows 2000.
Windows
Desktop (Executable Installer) - This file is
an installer for the Eve Virtual Machine. Note that an uninstaller for removing
the VM is included with the installation. The standard Windows Remove Programs
will not remove the VM.
Windows Desktop (Zipped
Files and Installer) - This file contains a single directory called Eve
which contains all the files for the VM. To install simply place this directory
anywhere on your hard drive (e.g. "C:\Program Files") and then
execute the Eve.exe or Evew.exeprogram.
You must execute this application to correctly install
the VM.
The VM on the desktop consists of the following components:
|
Eve.exe |
The native Eve VM itself, console version. |
|
Evew.exe |
The native Eve VM itself, non-console version. |
|
EveSync.exe |
The application that starts the EveSync connection between the desktop and a mobile device that has the Eve VM installed, over a connected ActiveSync connection. |
|
Eve.jar |
The Java version of the VM. This requires a Java 2 or higher Java VM to be installed on the system to work. |
|
JavaEve.exe |
A launcher for the Java version of the VM. |
The Java version of the VM is not necessary but because of the
excellent Just In Time compiler in the recent Java VMs
produced by Sun the Java version of the VM runs significantly faster than the
native version.
These builds are all ready to install and run. Each zip file contains a .CAB
file, which is the standard way of installing Windows Mobile applications.
Installing using the CAB file ensures that you can use the "Remove
Applications" feature to uninstall the VM if you wish. There are
instructions after the links on how to install the applications using the CAB
files.
For Developers: The individual VM files are
also present in the ZIP files in a subdirectory called "VM". You can
use these files to manually install the VM as well. Ensure that you run the
Eve.exe application wherever you finally install the application.
PocketPC/PocketPC Phones 2003 (Original Edition), Emulator Version
SmartPhone 2003
(Original Edition), Emulator
Version
PocketPC/PocketPC Phones 2003 Second Edition
SmartPhone
2003 Second Edition
Windows Mobile 5 PocketPC/PocketPC Phones.
Windows Mobile
5 SmartPhone.
Windows
Mobile 6 Classic/ Professional: PocketPC/PocketPC Phones.
Windows Mobile 6 Standard: SmartPhone Devices.
Windows
CE 5 Standard SDK (StrongARM/XScale Processor)
Windows CE 5 Standard SDK (MIPS Processor)
Windows CE 5 Standard SDK (SH4 Processor)
Windows CE 5 Standard SDK (Emulator)
1. Connect
the device to the desktop via ActiveSync.
2. Use
the "Explore" button to get a window into the "My
Documents" folder.
3. Drag
the CAB file to this directory.
4. On
the Pocket PC go to Start->Programs->File Explorer
5. Use
the File Explorer to navigate to the "My Documents" folder and click
once on the CAB file in the display.
6.
The application will then be installed and the CAB
file automatically deleted.
1. Connect
the device to the desktop via ActiveSync.
2. Use
the "Explore" button and then go into to the "My
Smartphone" icon.
3. Navigate
to the \Storage\Windows\Start Menu\Accessories folder.
4. Drag
the CAB file to this directory.
5. On
the SmartPhone use Start to get the
applications menu and go into the Accessories folder.
6.
Click on the CAB file to start the installation and
delete the CAB file when complete.
1. Connect
the device to the desktop via ActiveSync.
2. Use
the "Explore" button to get a window into the "My
Documents" folder.
3. Drag
the CAB file to this directory.
4. On
the device use the File Explorer to navigate to the "My Documents"
folder, and double-click on the CAB file.
5.
The application will then be installed and the CAB
file automatically deleted.
This file: Eve-142-Linux-x86.tar.gz
contains builds for Linux on x86 computers targeted for GTK2, X-Windows and
Command Line (no GUI) systems. They execute on Ubuntu
and Puppy Linux but are not guaranteed to execute on all Linux x86 platforms.
Source code and instructions to build the VM for different Linux systems is
provided in the Source Code section below.
This file: evevm-1.42-i386.zip contains a Debian installer that can be used to install the GTK-2
version of the Eve VM to a compatible Linux system.
There are Debian
installers for the Nokia
N800/N810/N900 Mobile Devices and for the x86
Emulators (for developers). Each of these is a zip file containing the deb files for the device.
For manual installation of the VM, use
these files: N800, N810, N900. Each contains the device (ARM) and emulator (x86)
builds of the VM.
This is separated into three parts:
Eve-142-SDK-Library.zip is the class library
needed to compile, run and debug Eve applications within an IDE (such as
Eclipse) or on the command line. It also includes a C++ header file for writing
Eve Native Interface files.
Eve-142-SDK-API.zip
contains the javadoc API and Eve Programming Guides.
The programming guide is also available on-line here.
Finally, the EveMaker
application is used to create executable targets and installable packages from
Eve applications that you develop. There are two versions currently available:
InstallEveMaker142.exe is the Windows
installer for the EveMaker application. This
installation does not require the Eve VM to be installed on the target
computer.
EveMaker142-Jar.zip
is a pure Java version of the EveMaker application
and will run on any system with a Java 1.2 Runtime Environment installed.
evemaker142.x86.zip
and evemaker142.arm.zip contain Linux debian installers for the EveMaker
application. These require the Eve VM 1.42 to be installed on the target
system.
There are four sets of source code.
o
The Win32/Windows Mobile C++ source code for the native VM is
here: Eve-142-WindowsVmSrc.zip
o
The Linux C++ source code for the native VM is here: Eve-142-LinuxVmSrc.zip
o The source code for the
Eve library Java classes for the native VM is in the file called /classes/EveSrc.zip
in the SDK.
o The source code for the
Eve library Java classes for a Java 2 VM is in the file called /classes/JavaEve.zip
in the SDK.
Building the Linux VM
To build the Linux VM unzip the file to a location of your choice, open
a terminal and go into one of the make-xxx subdirectories. Choose one
that is closest to your target system. Then run "make eve" to
compile the VM. If successful test the VM by doing:
eve ../lib/eve-desktop.eve
If this successfully brings up the desktop user interface try this:
eve -p5 -r
../lib/eve-desktop.eve
This should bring up the PocketPC emulated
version of the VM. Pressing the Menu button at the bottom left will
bring up a menu. You should hear a “pop” when the menu is displayed (this only
happens when the -r option is used). This lets you know that the audio
output of the VM is working properly.
To deploy the VM simply rename either eve-desktop.eve or eve-mobile.eve
(whichever you believe is more appropriate) to eve.eve and then
distribute that eve.eve file along with the executable eve file. Once the two
co-exist in the same directory the eve executable will be able to locate and
use that library without needing a specific command line option to tell it
which eve file to use. So you would be able to run:
eve -p5
on the command line and it should
work successfully once the eve.eve file is in the same directory.
For more advanced help on building the VM please join the Forum.