Finding what you need in the OCAP build.

在OCAP构建中发现需要的内容。

Build structure of the OCAP implementation.

构建OCAP实现的结构。

All you have to do is set things up for the OCAP RI.

您需要做的就是为OCAP RI进行设置。

You are almost ready to start building OCAP applications.

您几乎已经准备就绪，可以开始构建OCAP应用程序了。

The OCAP RI locates an application using two main files.

OCAP RI使用两个主要的文件查找应用程序。

Part 3 in this series describes how to build the OCAP ri.

本系列第三部分将介绍如何构建这种OCAP RI。

VLC is now ready to be run automatically from the OCAP RI.

现在VLC便可以自动从OCAP RI运行了。

The OCAP RI is an example of how to implement an OCAP stack.

OCAP RI 是一个如何实现 OCAP 堆栈的例子。

The next step is to convince the OCAP RI to run your application.

下一步是说服ocap RI来运行您的应用程序。

It's useful if you want to run the OCAP stack with a minimum of setup.

如果您想使用最少的安装运行这个OCAP堆栈，这将非常有用。

The OCAP RI window and the command-line window will both disappear.

此时 OCAP RI 窗口和命令行窗口都将消失。

The full source code is available if you want to build the OCAP RI yourself.

如果您想自行构建 OCAP RI，那么可以使用完整的源代码。

First, you need to understand how the OCAP RI decides which application to run.

首先，您应该理解ocap RI是如何确定运行哪一个应用程序的。

As the OCAP RI runs, it automatically stores an output log in the RILog.txt file.

OCAP RI在运行时，会自动在RILog . txt文件中存储一个输出日志。

The actual value of OCAPROOT depends on where you installed the OCAP ri binaries.

OCAPROOT的实际值取决于OCAP ri二进制文件的安装位置。

This is the same OCAP ri that you downloaded and installed in Part 1 of this series.

这个OCAP RI就是您在本系列的第1部分中下载并安装的。

When you shut down the OCAP ri, a script (batch file) tries to shut down VLC as well.

当您关闭ocap RI时，也会有一个脚本(批处理文件)试图关闭VLC。

The OCAP stack has a long history, which means it's made up of many different pieces.

ocap堆栈由来已久，也就是说，它是由许多片段组成的。

From an application perspective, it's helpful to consider OCAP as a collection of APIs.

从应用程序的角度而言，将OCAP考虑成一个API集合比较有用。

But although it's helpful to think of OCAP as an API stack, it is an oversimplification.

不过，尽管将OCAP想象成一个api堆栈比较有用，但这过于简单了。

If you used the default installation location, the value is /CableLabs/tru2way/ocap-ri/ocap.

如果使用默认安装位置，这个值就是 /CableLabs/tru2way/ocap-ri/ocap。

One important location is OCAPROOT, which is the root of the OCAP implementation source code.

一个重要的位置就是OCAPROOT，它是OCAP实现源代码的根。

Strictly speaking, OCAP is just a specification, so it is up to device manufacturers to implement it.

严格来讲，OCAP 只是一种规范，所以应该由设备制造商来实现它。

Eclipse takes care of rebuilding the project, packaging it correctly, and launching the OCAP RI.

Eclipse将负责重新构建这个项目，正确对其打包，并启动OCAP RI。

Keep that in mind as you work your way through building an OCAP application using command-line tools.

当您使用命令行工具来构建OCAP应用程序时，不要忘记这一点。

You now have a taste of what is possible with OCAP and the tools you need to create whatever you wish.

现在，您对 OCAP 的作用和实现您的想法所需的工具已有所了解。

The sheer complexity of the platform makes it hard for a would-be OCAP developer to know where to begin.

这个平台的复杂性使那些将要成为OCAP开发人员的人无从下手。

The OCAP RI goes hunting through each entry in the classpath, looking for a hostapp.properties file.

OCAP RI在此类路径中搜寻每个条目，查找hostapps . properties文件。

The OCAP RI you downloaded in Part 1 also runs on your desktop computer, but it's really a simulator.

您在第1部分中下载的OCAP RI也运行在您的桌面计算机上，但它的确是一个模拟器。

If your JDK or OCAP ri are located in different directories, you'll have to adjust the script accordingly.

如果您的jdk或ocap RI位于不同的目录中，则需要相应调整脚本。