Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
9 contributors

Users who have contributed to this file

@dorodnic @ev-mp @DavidGoedicke @yousseb @wspr @VasuAgrawal @matkatz @carypai @bfulkers-i
42 lines (29 sloc) 2.16 KB

macOS Installation

Note: macOS support for the full range of functionality offered by the SDK is not yet complete. If you need support for R200 or the ZR300, legacy librealsense offers a subset of SDK functionality.

Note: The T265 tracking module is not yet supported on macOS via librealsense. Support is planned to be added in a future release.

Building from Source

  1. Install CommantLineTools sudo xcode-select or download XCode 6.0+ via the AppStore
  2. Install the Homebrew package manager via terminal - link
  3. Install the following packages via brew:
  • brew install cmake libusb pkg-config
  • brew cask install vulkan-sdk

Note librealsense requires CMake version 3.8+ that can also be obtained via the official CMake site.

  1. Generate XCode project:
  • mkdir build && cd build
  • sudo xcode-select --reset
  • cmake .. -DBUILD_EXAMPLES=true -DBUILD_WITH_OPENMP=false -DHWM_OVER_XU=false
  1. Build the Project
  • make -j

Note: On some Mac systems you might encounter ld: library not found for -lusb-1.0 error (either in the terminal during make or in XCode) This can be worked-around by setting environment variable: /bin/launchctl setenv LIBRARY_PATH /usr/local/lib

Note: You can find more information about the available configuration options on this wiki page.

What works?

  • SR300, D415 and D435 will stream depth, infrared and color at all supported resolutions
  • The Viewer, Depth-Quality Tool and most of the examples should work

Packaging your application

  1. librealsense requires libusb to be bundled in the application. To fix the real-time linking, use install_name_tool
install_name_tool -change /usr/local/opt/libusb/lib/libusb-1.0.0.dylib @rpath/libusb-1.0.0.dylib librealsense2.dylib
  1. Copy libusb-1.0.0.dylib and librealsense2.dylib to your application's Frameworks folder

What are the known issues?

  • Changing configurations will often result in a crash or the new configuration not being applied (WIP)
You can’t perform that action at this time.