Installation
Overview
The BMC C++ SDK Windows installer sets up the necessary components for the SDK on the system. This includes:
A dynamic library:
bmc_sdk.dll
on Windowslibbmc_sdk.dylib
on macOSlibbmc_sdk.so
on Linux
A static library:
bmc_sdk_static.lib
on Windowslibbmc_sdk_static.a
on macOSlibbmc_sdk_static.a
on Linux
Example applications to test the SDK
Header files for integration (
include
directory)
Prerequisite
As a prerequisite, the C++ SDK requires having the BinhoMissionControl Bridge (BMC Bridge) utility installed and added to the PATH environment variable.
To improve modularization and streamline our update process, we've decided to separate the Bridge from the BMC C++ SDK. The Bridge, which connects high-level interfaces like Binho Mission Control to our host adapters, is updated frequently. By decoupling it from the BMC C++ SDK, we can deliver more focused updates to each component. Additionally, as we continue to meet the growing demand for a native C/C++ SDK, we're also planning to open-source the BMC C++ SDK to further empower the developer community.
Windows
Download BMC Bridge installers: - BMC Bridge 1.0 for Windows 32-bit - BMC Bridge 1.0 for Windows 64-bit
Once installed, proceed with the following setup instructions:
The bridge is typically installed in
C:\Program Files (x86)\BinhoMissionControlBridge
Add this path to your system's PATH environment variable.
Press
Win + R
, typesysdm.cpl
, and press Enter.Go to the Advanced tab, and click on Environment Variables.
In the System variables section, find the PATH variable, select it, and click Edit.
Click New and add
C:\Program Files (x86)\BinhoMissionControlBridge
To verify the installation, open Command Prompt and execute:
bridge --version
macOS
Download macOS binaries: - Bridge 1.0 macOS binaries for ARM - Bridge 1.0 macOS binaries for Intel
Extract the binaries and place the extracted folder in a location of your choice.
Open a Terminal window and navigate to the directory where you extracted the binaries.
To make the binaries easily accessible, add the directory to your PATH environment variable. You can do this by editing your
~/.zshrc
(for Zsh users) or~/.bash_profile
(for Bash users) file:nano ~/.zshrc
or, if you use Bash:~/.bash_profile
Add the following line at the end of the file:
export PATH=/path/to/your/extracted/folder:$PATH
Replace/path/to/your/extracted/folder
with the actual path to the extracted folder.Save the file and apply the changes by running:
source ~/.zshrc
or, for Bash users:source ~/.bash_profile
To verify the installation, run the following command in Terminal:
bridge --version
Installation of the C++ SDK
Windows
Setup instructions
Add
C:\Program Files (x86)\BinhoMissionControlSDK
to your system's PATH environment variable.
Download the Installer: - BMC C++ SDK 1.1.0 for Windows 32-bit - BMC C++ SDK 1.1.0 for Windows 64-bit
Run the Installer: Double-click on the installer and follow the on-screen prompts.
Installation Directories: By default, the SDK will be installed into the
c:\Program Files (x86)\BinhoMissionControlSDK
directory. Inside this directory, you will find:bmc_sdk.dll
: The SDK dynamic link library.bmc_sdk_static.lib
: The SDK static library.README.md
: Read-me file in markdown format for users.examples
: A directory containing example applications.include
: A directory containing various header files necessary for SDK integration.
Add to PATH Environment Variable. For the applications to function correctly: Both the
bridge
and the BMC C++ SDK installation directories must be added to the system's PATH environment variable.Integration: To integrate the BMC C++ SDK into a project:
Reference the SDK library using the static or dynamic library files.
Include necessary headers from the
include
directory.
Test the Example Applications: After setting up the PATH, you can run the example applications in the examples directory.
macOS
Download macOS binaries: - BMC C++ 1.1 macOS binaries for ARM - BMC C++ 1.1 macOS binaries for Intel
Extract the binaries and place the extracted folder in a location of your choice.
To verify the installation, run the example applications in the examples directory.
Installation Directory Structure
Last updated