You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Table of Contents

This page presents a high level overview and instructions for building the various components of the OCAP Reference Implementation as well as supporting tools, which include

  • PC Platform Emulator
  • OCAP Stack
  • HE4RI
  • Common Source
  • atelite
  • tru2way Workbench

You should always compile changes to the RI Platform before compiling changes to the OCAP stack.

Build Environment Summary

More detailed instructions on how to set up your complete build environment can be found at RI Build Environment.

NOTE: he4ri is not required to run the platform..leaving this section in place in case he4ri is once again required to run the platform

From a build perspective the key environment variables to understand are

Building the Various RI Components

Platform Build & Test Run

  • cd $PLATFORMROOT
  • make
    • does not give success response, last line says "make[1]: Leaving directory '/cygdrive/.../RI_Platform/launcher'
    • to determine success, look in \trunk\ri\RI_Platform\install\Win32\debug\bin on Windows to see if ri.exe was built
  • executing
    • build stack - see below
    • configure and run HE4RI (see below) - it must be running before you start the platform
    • edit ./platform_win32.cfg on Windows or ./platform_linux.cfg on Linux, and change variable RI.Platform.he4riServer to your PC's IP address. Use your ethernet card's IP address, 127.0.0.1 does not work.
    • ./runPlatform.sh

NOTE: he4ri is not required to run the platform and to run the smoke tests, we can use the shunt that is built in platform by default. Please find the procedure to run the smoke tests using shunt in running smoke tests section.

For more details about platform make targets see RI PC Platform Build Targets

OCAP Stack Build

  • NOTE: by default JVM will not be compiled. To enable JVM compiling do the following:
    • In $OCAPROOT/target/$OCAPTC/buildrules.properties comment out the following value: build.jvm.exclude=true
  • cd $OCAPROOT
  • ant

NOTE: if you are building the JVM (true by default on Linux) and you are starting from a fresh checkout or after a clean you will get an error:

[exec] make: *** No rule to make target `obj/bcattr.o', needed by
`jvm/phoneME/phoneME_040809/build/mpe-x86-cygmingw/./bin/libcvm.dll'. Stop.

This is a known issue. The workaround is to build again (e.g. execute "ant build").

HE4RI Build and Test Run

  • not needed-see note at top of page
  • cd $HE4RIROOT
  • ant clean compile deploy
  • cd temp
  • ./runHe4ri.bat

HE4RI Precompiled Zip

  • not needed-see note at top of page

For developers that do not need to work on the HE4RI directly, there is a zip file which is precompiled.

  • in trunk\emu\HeDri\Emulator\deploy extract the HE4RIDeploy.zip to the current directory
  • modify the configuration parameter for the HE4RI IP address see: Running the Reference Implementation
  • run the runHe4ri.bat which is extracted from the zip to the deploy directory

tru2way Workbench

Image Map Editor

The image map editor is a tool used to create the remote and front panel user interface meta-data employed by the RI Emulator.

To build this tool, the following environment variables must be set:

  • RISDKROOT: directory from which to perform SDK build commands
  • RISDKTC: extension from $RISDKROOT/target (such as Win32/debug)
  • RISDKHOST: target host environment (such as Win32)
  • RI_BUILD_SUPPORTLIBS: flag to build supporting libraries

To build the Image Map Editor:

  • cd $RISDKROOT/3rdParty
  • make (be sure that RI_BUILD_SUPPORTLIBS=1)
  • cd $RISDKROOT/ImageMapEditor
  • make

The result is placed in $RISDKROOT/install/$RISDKTC/bin/imeditor

atelite

  • No labels