libusb library troubles in MACOS 10.10

Home Forums AR Sandbox Forum libusb library troubles in MACOS 10.10

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #100780

    Currently working on setting up the VR Sandbox within a quadcore mac running macos 10.10.2. (Forgive improper use of nomeclature) Initially attempted to use the [bash -c “$(curl -fsSkL”] command to assist in the Build process but I was unfamiliar with how to manually resolve the command response [::: Requires Mac OS X 10.6 Snow Leopard, 10.7 Lion, or 10.8 Mountain Lion.] within the makefile. So I moved onto processing the commands manually.

    1st I had to install libusb support/topology query support using the tarball
    following that I arrived at trouble with response while processing the sudo make command for the Kinect-2.8 package.

    I receive multiple instances of the following 2 errors

    warning: zero size arrays are an extension [-Wzero-length-array]
    warning: commas at the end of enumerator lists are a C++11 extension [-Wc++11-extensions]

    Any assistance would be appreciated.

    I’ve adjusted my file to contain references to the following folders to accomodate the libusb install. Don’t know that I did it right, as now when I attempt to run the make command for the Vrui using this updated Buildroot file, it replies with not finding USB support, nor the ability to search for topology.

    LIBUSB1_BASEDIR = $(shell $(/usr/local)/ libusb-1.0/libusb.h libusb-1.0.$(DSOFILEEXT) $(INCLUDEEXT) $(LIBEXT) $(SYSTEM_PACKAGE_SEARCH_PATHS))
    LIBUSB1_INCLUDE = -I$(/usr/local/include)/$(INCLUDEEXT)
    LIBUSB1_LIBDIR = -L$(usr/local/lib)/$(LIBEXT)

    I previously got this to run on dual core imac without water renders and never had these types of library issues.

    Thank again for anytime given or consideration.

    Oliver Kreylos

    warning: zero size arrays are an extension [-Wzero-length-array]
    warning: commas at the end of enumerator lists are a C++11 extension [-Wc++11-extensions]

    I have not tried building the Vrui / AR Sandbox software stack on Mac OS 10.10. But so far, every new version of Mac OS has broken a few things here and there. These warnings are OK to be ignored, but I will look into the source code to get rid of them. Would you please post the complete output from the compiler for the source file where these warnings occur, including line numbers? Without that, I will have a hard time tracking them down.


    In cases like this, where you know exactly where a certain library is installed, you can set up the package file entry like this:

    LIBUSB1_BASEDIR = /usr/local
    LIBUSB1_INCLUDE = -I/usr/local/include
    LIBUSB1_LIBDIR  = -L/usr/local/lib
    LIBUSB1_LIBS    = -lusb-1.0

    (Ensure that /usr/local/lib indeed contains the libusb-1.0.dylib library file.)

    After this change, Vrui’s makefile should auto-detect the presence of bus topology calls. If it doesn’t, you can explicitly enable that feature via line 82 in the makefile:

    # Presense of libusb_get_parent in libusb.h:

    Uncomment the second line and set the value to 1.

    This should hopefully work.


    Thank you again for all the time and effort that went into the project. This is an update that we went a different route to get a better result.

    In the case originally explained we ran into issues using 10.10.2 and running the[bash -c “$(curl -fsSkL”] command. Unfortunate of us that the harddrive that was running that os suffered a failure and needed replacing.

    We replaced the drive and instead of reloading 10.10.2 we loaded 10.6 which is supported.. the rest of the setup went with out issue. .. when it came time to use Xcode.. we were required to update to 10.10.2 as a result of Apples restrictions. Thankfully we had already done the preliminary work with your Vrui script and completed all steps after the Vrui curl command within 10.10.2

    If another mac user attempts it we used a 2009 mac pro with 1GB video , quad core. For best implementation use 10.6 as the os you start with.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed.