Navigation

    Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Unsolved
    1. Home
    2. Tags
    3. dylib
    Log in to post

    • UNSOLVED Mac - Qt Dylib locations... ?
      General and Desktop • cmake mac linking bundle dylib • • Dariusz  

      6
      0
      Votes
      6
      Posts
      135
      Views

      @Dariusz You should use macdeployqt for all things qt, possibly your custom solutions for your custom stuff (additional libs, etc).
    • SOLVED How Can I link custom .dylib library in to another project in iOS?
      3rd Party Software • macos link error 3rd party dylib • • Yash001  

      4
      0
      Votes
      4
      Posts
      2514
      Views

      @SGaist Thank you sir for your advise. I solve this issue. By mistake, I put the " \ (backward slash)" before LIBS variable in ChargeDischarge2 .pro file. Now project ChargeDischarge2 is build.
    • UNSOLVED How To Call Qt/C++ OSX Dylib from Objective C
      General and Desktop • c++ osx objective-c dylib cocoa • • maximo  

      10
      0
      Votes
      10
      Posts
      4597
      Views

      @SGaist said: QMacCocoaViewContainer Hmmmm! Interesting! I'll have to give this some thought.
    • dyld: Library not loaded when debugging but ok when running (on OS X El Capitan) [SOLVED]
      General and Desktop • debug osx dylib • • ucmar  

      10
      0
      Votes
      10
      Posts
      4139
      Views

      ok after some further research I have found this page (probably the one you @SGaist were referring to) https://forums.developer.apple.com/thread/9233. As you mentioned, it seems that DYLD_* variables have been disabled (they are ignored) since El Capitan because of a new feature called System Integrity Protection (SIP). According to Apple Developer website, debugging can be happily performed only by Xcode (although I haven't tried it yet). What about Qt? Will 5.5.1 or 5.6 allow debugging on El Cap with SIP? I read on another page SIP can be disabled in Recovery mode. Anyway, I am not keen at hacking my own system... the alternative is to wait for the next version of Qt and hope for a solution. Unsure what to do for now, in the meanwhile I am stuck! Grrr UPDATE: I ended up disabling SIP following the following step: Enter Recovery mode (Cmd+R on startup) Open Terminal csrutil disable; reboot Now debugging went back to normality! My only doubt is that when i do csrutil status, I receive the following message: "System Integrity Protection status: enabled (Custom Configuration). Configuration: Apple Internal: disabled Kext Signing: disabled Filesystem Protections: disabled Debugging Restrictions: disabled DTrace Restrictions: disabled NVRAM Protections: disabled This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state." Not very reassuring uh? (and why is that still saying SIP enabled?)
    • Are there .pro settings so as to avoid using install_name_tool all the time?
      Installation and Deployment • qtcreator qt5.5 osx yosemite pro dylib installnametool • • maximo  

      2
      0
      Votes
      2
      Posts
      825
      Views

      Hi, Please practice some patience, this forum is community driven so waiting 24 to 48 hours is normal. In order to avoid fragmentation, let's keep the questions and answers in only one thread. Closing this one.
    • [SOLVED] OSX Deployment Fatal Error with DyLib -- Library Not Loaded / Image Not Found
      Installation and Deployment • qt5.5 library dylib librarypath not found dynlib library not loa image not found • • maximo  

      5
      0
      Votes
      5
      Posts
      6708
      Views

      You can also set DYLD_FRAMEWORK_PATH before launching your application