Pleora Technologies Inc. eBUS SDK v6.2.8.5877 API



Building and running

Windows

Building and Running C++ Samples

  1. Copy the samples from C:\Program Files\Pleora Technologies\eBUS SDK\Samples to a folder you have write permissions to.
  2. Open any of the samples using Visual Studio 10 or higher.
  3. Build the sample using F7 or the assigned build command key.

Creating and Building your Own Applications

  1. Create a C++ project using Visual Studio 10 or higher.
  2. Add $(PUREGEV_ROOT)\Includes to the header files path.
  3. Add $(PUREGEV_ROOT)\Libraries to the linker libraries path.

You do not need to manually add any of the eBUS SDK link libraries to your project. #pragma import lib statements are used throughout the header files to automatically add all eBUS SDK link libraries to your project.

Running your Applications

Samples and your applications will run as long as you have the common files eBUS SDK folder (32-bit or 64-bit) is included in the PATH environment variable. It is also possible to run an application if the eBUS SDK common files are copied to the same folder as the application binary.

Linux

Building and Running C++ Samples

  1. At the command line, browse (cd) to the bin directory (/opt/pleora/ebus_sdk/<OS>/bin)
  2. source the set_puregev_env script (source set_puregev_env).
  3. Browse (cd) to the folder of the samples (/opt/pleora/ebus_sdk/<OS>/share/samples).
  4. run ./build.sh as root to build all samples
  5. The generated binary is in the same folder as the sample, ready to be executed.

All samples use the same master makefile (sample.Makefile), which can be found in the samples folder. It is able to build pure command line samples and those using Qt, such as eBUSPlayer.

Building your Own Applications

You can look at the sample.Makefile for a makefile that can build applications using the eBUS SDK. You need to source the eBUS SDK environment as described in the in the "Building Samples or Your Applications on Linux" section before building against the eBUS SDK.

Important points to consider:

  1. You need to add the include path -I/include
  2. You need to add the library path -L/lib
  3. You need to link against the following libraries (may not all be required)
    1. -lPvBase
    2. -lPvDevice
    3. -lPvBuffer
    4. -lPvGUIUtils
    5. -lPvGUI
    6. -lPvPersistence
    7. -lPvGenICam
    8. -lPvStream
    9. -lPvTransmitter
    10. -lPvVirtualDevice

Running your Application

You can either source the set_puregev_script (source set_puregev_env) or create your own script to launch your application. For an example, you can look at the eBUSPlayer script, which launches the eBUSPlayer.bin application.

The script does the following:

  1. Sets the $PUREGEV_ROOT environment variable to the eBUS SDK bin folder.
  2. Defines the required GENICAM environment variables.
  3. Defines the location of the GENICAM cache folder.
  4. Adds the eBUS SDK lib folder to the libraries path.
  5. Adds the GENICAM libraries folder to the libraries path (Linux64_x64 or Linux32_i86).

OS X

Building and Running C++ or Objective-C Samples

  1. Copy the samples from /Library/Framework/eBUS.framework/Versions/Current/Samples to a folder you have write permissions to.
  2. Open any of the sample xcodeproj Xcode project.
  3. Build the sample by issuing the Command-B build command.

Creating and Building your Own Applications

  1. Create your new project in Xcode (Objective-C/Cocoa, C or C++)
  2. Add the eBUS Framework to your application

You do not have to play with environment variables, PATH or anything. Just including the eBUS Framework in your application should be enough.

When using the C++ API of the eBUS SDK from Objective-C code, you need to rename your .m files to .mm so they can interact with C++ code.

Running your Applications

If the eBUS Framework is installed in the default OS X frameworks location your application should be able to run from anywhere on the system.

It is also possible to run the application from a private eBUS Framework distribution. In order to do so, you need to have the eBUS Framework inside your application bundle. You then have to adjust the runtime search path of your application so it can properly locate the eBUS Framework in the application bundle.


Copyright (c) 2002-2021 Pleora Technologies Inc.
www.pleora.com