Jason, unfortunately that did not work either. Searching through the forum there was one post that eluded to @executable_path but not with an example. It sure would be nice if there was a recipe in the documentation for how to build and use a .dylib file. What hurts is that I did this years ago and I can vaguely remember that one of the secrets was to declare your c function as an extern so it would be visible (which I have tried). But at this point I can’t tell if the app can’t find the .dylib or can’t find the function.