Previous: Compiling the SDK

A number of example applications are provided to demonstrate the functionality available in the OpenJAUS SDK and are generally structured in server/client pairs. Most of the time, the server code will be run on the robot and the client code will be run on the operator control unit (OCU).

All JAUS Components built using the OpenJAUS SDK require a configuration file (*.ojconf) to operate correctly. If the configuration file does not exist, an exception will be thrown and the example application will terminate. Generally, configuration files are tailored to a specific application based on the number of JAUS Components. 

For the provided example applications, sample configuration files are provided in {openjaus sdk installation}/resource.  These sample configuration files are:

  • BaseDemo.ojconf : For use with the demo applications found in {openjaus sdk installation}/apps/core. (BaseDemo, EventsBaseDemo).
  • ExampleClient.ojconf : For use with all client demo applications. (GposClientDemo, PdClientDemo, etc)
  • ExampleServer.ojconf : For use with all server demo applications not in {openjaus sdk installation}/apps/core. (GposDemo, PdDemo, etc).

Compiling the Sample Projects

As with compiling the SDK itself, we use premake to generate the necessary files to compile the code. Depending on which examples you'd like to compile, you'll need to specify certain flags for premake.

To generate build infrastructure for BaseDemo and EventsBaseDemo, use -ojbase

.\premake4 --ojbase [vs2010/gmake/etc]

To generate build infrastructure for other example projects use --ojexamples

.\premake4 --ojexamples [vs2010/gmake/etc]

To generate build infrastructure for all projects use --ojall

.\premake4 --ojall [vs2010/gmake/etc]

More information about options for premake can be found by running

.\premake4 --help

Using the Sample Configuration Files

Option 1 [Recommended]

  1. Copy the appropriate .ojconf file(s) from {openjaus sdk installation}/resource to {openjaus sdk installation}/bin (or wherever the executable resides)
  2. Rename .ojconf file to the same name as the application to be executed.

Example: Running the GposDemo Application

  1. Copy ExampleServer.ojconf from {openjaus sdk installation}/resource  to  {openjaus sdk installation}/bin
  2. Rename to {openjaus sdk installation}/bin/ExampleServer.ojconf  to  {openjaus sdk installation}/bin/GposDemo.ojconf.
  3. Run the GposDemo application

Option 2 [Advanced]

The configuration file to be used can also be specified using the –-ojconf command line flag.

Example: Running the GposDemo Application

Assuming the GposDemo application is in the default location:

  1. Open a command line shell
  2. Go to {openjaus sdk installation}/bin directory
  3. Run the PdDemo application with the following command:
    • ./GposDemo –-ojconf=../resource/ExampleServer.ojconf

Modifying the Sample Configuration Files

The sample configuration files can be modified using the configuration editor tool. See Using the Configuration Editor for more information.

Previous: Compiling the SDK