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.
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.
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.
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:
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:
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.
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