Ocap Getting Started, part 3rd: building Ocap RI

The 1th and 2nd parts of this series give you an initial understanding of opencable application Platform Reference implementation (OCAP RI) from the perspective of the application developer. You learned how to run applications on the RI platform and how to create new applications for RI or other OCAP devices. This is the final issue, which describes the OCAP ri from a platform perspective and shows how to build Ri from the source file. With a deep understanding of the OCAP RI stack, you can optimize or enhance the platform, or migrate it to the hardware of your choice.

RI schema

OCAP RI uses the schema shown in Figure 1:

Figure 1. OCAP RI Architecture

The following information describes Figure 1:

The OCAP stack runs on the JVM, but some methods are implemented in local code. Accordingly, figure 1 separates the Java language portion of the OCAP stack from the local part of the OCAP stack.

The JVM runs Connected Device Configuration (CDC), Foundation profile (FP), and Personal basis profiles (PBP), as described in part 1th. OCAP RI's JVM uses an open source project phoneme Advanced's modified version.

The local implementation of the OCAP stack and the JVM itself is ported to a platform-independent layer of code, the multimedia Platform Extensions (MPE).

And MPE calls the platform-independent code of the Mpeos layer. Mpeos need to be ported to devices running on the OCAP stack.

The RI platform is a virtual device or Device Emulator. The RI platform itself can be built and run on Windows or Linux platforms to form a Device Emulator. When using the Mpeos implementation based on the RI platform, you get a practical OCAP stack that runs on a Device emulator on a desktop computer.

Next, I'll show you how to build OCAP RI on Windows.

Tools

OCAP RI must be built in a class Linux environment. The basic building tools are:

make

gcc

Java compiler

Ant

To build OCAP RI on Windows, you need to install 3 packages:

Cygwin

Java Development Kit (JDK)

Ant

Cygwin