dylib

I've compiled a dylib in Qt/C++. I created a simple class method called test() that reads a string input and returns a string output with "-response" back. Now how do I load that inside Objective C in XCode 7 (a default Cocoa application) and make it emit test() via NSLog() ? This is what my build folder looks like in Qt/C++. You need to use an Objective-C++ class, which is a hybrid of Objective-C and C++. The greatest challenge using one or more Objective-C++ classes in a largely Objective-C project is avoiding exposing C++ classes to the Objective-C classes. Therefore you need to avoid C++

I have a dynamic library which I load using dlopen() and then unload using dlclose() ; If I dont include any objective c code dlopen() needs one dlclose() call which is expected behavior. But when I include any objective c code to target, I have problem that I need to do two dlclose() calls to the loaded library in order to unload. Is this something expected behavior? How can I fix it? I realize that you are using dlopen , not CFBundle or NSBundle . Nevertheless, the Code Loading Programming Topics manual says this: In Cocoa applications, you should not use CFBundle routines to load and unload

I'm still quite new to Objective C and Xcode, but I just finished a small app that uses the openCV libopencv_core.2.4.2.dylib . When I went to open the final built app on another machine , OS X threw me this error: Dyld Error Message: Library not loaded: */libopencv_core.2.4.dylib Referenced from: /Users/USER/Desktop/my app.app/Contents/MacOS/my app Reason: image not found Why is my app looking for 2.4 instead of 2.4.2 here? What I already checked: I added a new build phase -> so that libopencv_core.2.4.2.dylib is copied to the app package (via "Copy Bundle Resources" in Xcode) - libopencv

I have a third party OS X dylib that I'm using in my app and don't have easy access to its creator. I'd like to determine if it was linked with -flat_namespace. Is that possible? If so, how? Run otool -hV on the library. If you don't see TWOLEVEL , then it was linked with -flat-namespace . For example: twolevel.dylib: Mach header magic cputype cpusubtype caps filetype ncmds sizeofcmds flags MH_MAGIC_64 X86_64 ALL 0x00 DYLIB 8 672 NOUNDEFS DYLDLINK TWOLEVEL NO_REEXPORTED_DYLIBS versus flat.dylib: Mach header magic cputype cpusubtype caps filetype ncmds sizeofcmds flags MH_MAGIC_64 X86_64 ALL

I am new to Xcode and Mac environment. I am using some dynamic and static libraries like boost, Clucene, etc. I have all the libraries under MyApp.app/Contents/Resources I want to set this path as the app's dyld_library_path. I tried editing XXX.plist file like DYLD_LIBRARY_PATH /mypath/xxx and setting the environment variable and argument in Xcode Nothing work. but if I run a shell script like below without double clicking the app in my .dmg it works #!/bin/bash clear cd /Volumes/xxx/myapp.app/Contents/MacOS export DYLD_LIBRARY_PATH="/Volumes/xxx/myapp.app/Contents/Resources" ./myapp I am

I've a framework with a dylib in my iOS app which was compiled on another machine. I checked out the sources on my machine and tried instructing lldb to map the source code path using: settings set target.source-map /source/code/path/in/dylib/prefix /source/code/path/on/my/machine/prefix To no avail, still seeing assembly. Note #1: the dylib was compiled from C++ code in the same version of Xcode. Note #2: I'm used nm -pa /path/to/dylib to determine whether file paths are embedded into the debug info, and they are, lldb doesn't play along for some reason. Thanks UPDATE I've followed Jim Ingham

I need to create a Mac version of our libraries for one of our customers. I am not so familiar with dynamic libraries on Mac, but from what I understand, I have 2 options: .dylib or frameworks. What would be the best option? Why? Few related questions: If I understand correctly, .dylib have to be installed in one of the stnadard UNIX directories such as /usr/lib, etc. Hence using a .dylib should make my customer's installer much more complex, since they'll probably need to request permission to write something in a system folder? Can frameworks be private and embedded within my customer's

I am developing a plug-in bundle , say MyPlugIn.bundle for an application , say BigApp.app . This bundle requires a dylib , say MyPlugIn.bundle/Contents/Resources/library.dylib . I have relocated paths for library.dylib, as I would have done for a simple application bundle: $ otool -L MyPlugIn.bundle/Contents/MacOS/MyPlugIn MyPlugIn.bundle/Contents/MacOS/MyPlugIn: @executable_path/../Resources/library.dylib (compatibility version 0.0.0, current version 0.0.0) [...] $ otool -L MyPlugIn.bundle/Contents/Resources/library.dylib MyPlugIn.bundle/Contents/Resources/library.dylib: @executable_path/..