Intel RealSense SDK is using CMake eco-system to offer useful customization to customers who wish to build the SDK from source.
For example, to generate makefile with
BUILD_EXAMPLES flag turned-on, use the following command line:
cmake .. -DBUILD_EXAMPLES=true.
cmake-gui utility to configure and generate your build files.
Build SDK examples and tools
Controls the-subset of examples and tools dependent on OpenGL. Disabling this option will reduce the set of tools and examples to
rs-fw-logger. Recommended for headless systems without the graphic subsystem.
Build the full suite of unit-tests for the SDK.
When enabled, YUY to RGB conversion and Depth-Color spatial alignment will take advantage of multiple-cores using
OpenMP. This can reduce latency at expense of greater CPU utilization.
Having UVC per-frame metadata requires building with Windows SDK installed. When this flag is disabled, the resulting binary might not be capable of properly parsing UVC metadata if Windows SDK was not installed during the build. If this flag is true, not having Windows SDK install will break the build.
Build Python bindings for the SDK. Requires Python to be installed. See wrapper page for more information.
Build Node.js bindings for the SDK. Requires Node.js to be installed. See wrapper page for more information.
Setting this flag to true will configure the underlying backend to use
libuvc. This backend is default for Mac OS, but can be configured on other OS-s as well.
libuvc can serve as a more robust alternative to the native backend, however, it has well known limitations and is not recommended to be used in end-products.
When this flag is enabled, all API-calls will be written to the log at
INFO severity. This will include any errors, duration, input and output parameters as well as the return value. Entry and exit from API calls will be documented as well at
DEBUG severity. Enabling this feature will result in severe performance penalty.
When this option is enabled, hardware commands will be dispatched through extension-unit (XU) transfer protocol. When disabled (and assuming the hardware supports it) the SDK will talk to the hardware directly using
When enabled the output of the library will be a dynamic link library (DLL) or a shared object (SO). When disabled the output will be a static library (LIB/A).
Desired build time. To take advantage of compiler optimizations set to "Release" or "RelWithDebInfo".
When enabled frames that do not require processing will not be mem-copied on arrival, rather the
rs2::frame object will track native handle to the underlying OS resource (be it V4L2 video-buff or an
ISample). This will reduce CPU utilization and save battery life, but can introduce unexpected latency or frame-drops, since the responsibility for buffer lifetime management falls on the application developer.
Perform cross-platform logging using EasyLogging++ 3rd-party library.
Search for OpenCV 3rd-party and include examples under
wrappers/opencv in the project.
Search for PCL 3rd-party library and include example under
wrappers/pcl in the project.
Assuming you received from Intel an engineering sample of V200 (TM2) device with its drivers, enable support for it in the SDK.
When enabled increases binary footprint but prevents the dependency on Visual C++ Redistributables.
Updated about a year ago