• jancsika

    Oh-- remove the "-verbose" flag we used to debug the issue.

    Also note-- you're version of helios is probably finding the libusb dylib in the homebrew lib directory. So if you use your same patch on a machine where you didn't install homebrew, helios will no longer work.

    Nevertheless-- glad to hear you've got it running!

    posted in extra~ read more
  • jancsika

    @didipiman Note: you can also use the script purr-data/packages/darwin_app/embed_MacOSX_dependencies.sh from the repo as a reference for how this works.. IIRC it only looks for deps that have homebrew path, so I'm not sure that it will properly pick up that libusb dylib. But you can at least have a look at the script to see how it works.

    posted in extra~ read more
  • jancsika

    @didipiman Sounds good.

    One thing you can do is use otool to inspect the paths for a pre-existing external library that has a dependency. Try fluid~:

    1. Make sure fluid~ will instantiate properly on a canvas.
    2. Find the fluid~ lib in your Purr Data app bundle. Use otool -L to inspect its dependencies. It should have a dependency on a fluidsynth library which I ship with Purr Data.
    3. Go to the directory in the app bundle where that fluidsynth lib lives.
    4. Use otool to figure out its install name

    Once you get that info, put your libusb dylib library in the exact same directory inside the app bundle as the fluidsynth library. Then use install_name_tool/otool to set the same path relationship helios and libusb binaries that you saw with fluid~ and fluidsynth

    I'll try to do the same the next time I get access to a mac machine.

    posted in extra~ read more
  • jancsika

    @didipiman For some reason the library isn't finding that libusb-1.0.0.dylib dependency. You'll need to fish around the OSX docs about install_name_tool to figure out how to ensure it's in the correct search path.

    posted in extra~ read more
  • jancsika

    @didipiman I don't really understand Macos' toolset. Give this a try and see if you can instantiate the object afterward:

    install_name_tool -id /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/libusb-1.0.0.dylib /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/libusb-1.0.0.dylib

    posted in extra~ read more
  • jancsika

    @didipiman Oops, try this:

    otool -D /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/libusb-1.0.0.dylib

    posted in extra~ read more
  • jancsika

    file /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/libusb-1.0.so

    posted in extra~ read more
  • jancsika

    @didipiman Hm.

    Try:

    install_name_tool -id /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/libusb-1.0.so /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/libusb-1.0.so

    posted in extra~ read more
  • jancsika

    @didipiman How about:

    otool -D /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/libusb-1.0.so

    posted in extra~ read more
  • jancsika

    @didipiman And now this:

    otool -D /Applications/Pd-l2ork.app/Contents/Resources/app.nw/extra/pd_helios/helios.pd_darwin

    posted in extra~ read more

Internal error.

Oops! Looks like something went wrong!