Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Upgrading to 5.5 on Mac causes cocoa error
Forum Updated to NodeBB v4.3 + New Features

Upgrading to 5.5 on Mac causes cocoa error

Scheduled Pinned Locked Moved General and Desktop
5.5mac
6 Posts 2 Posters 2.3k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W Offline
    W Offline
    wesblake
    wrote on last edited by
    #1

    We have an application, HTML5 project type. Developed using Xcode by using the Qt provided script to convert a Creator project.
    The app was started on 5.3. Upon release of 5.4, I was able to switch with a simple perl expression on my project folder:
    perl -p -i -e 's//5.3///5.4//g;' grep -ril --exclude=*.o /5.3/ *

    I tried doing this the last couple days to update to 5.5. The first problem I ran into was a complaint about not finding QtWebChannel, something we never needed before, but fine, I added the framework to the project.
    After that, I'm stuck on the following no matter what I do (this is just running from Xcode, no exported bundle yet):

    This application failed to start because it could not find or load the Qt platform plugin "cocoa".

    Available platform plugins are: cocoa, minimal, offscreen.

    Reinstalling the application may fix this problem.
    (lldb)

    Ive searched and searched and all the related answers have to do with final bundle, this is something to do with 5.5 specifically.
    I can use the same command to switch back to 5.3 or 5.4 and everything works again, both running from Xcode and a final exported application bundle. So what's changed in 5.5 that I'm missing? Thanks.

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi,

      IIRC, the runtime path handling has changed. Take a look with otool -L to your Qt libraries.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      W 1 Reply Last reply
      0
      • SGaistS SGaist

        Hi,

        IIRC, the runtime path handling has changed. Take a look with otool -L to your Qt libraries.

        W Offline
        W Offline
        wesblake
        wrote on last edited by
        #3

        @SGaist
        You are correct. If I run otool -L on 5.3 or 5.4, I get full path. If i run it on 5.5 frameworks, I get @rpath
        However, I still can't figure out what/how to change to solve for this. I already have a script I run on final app bundles to fix them for deployment that changes everthing to @executable_path but it still doesn't work with 5.5
        After my script, I can check with otool -L and everything looks great, same error. Ideas? I'll go through one by one and see if maybe something's off I suppose.

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #4

          Did you also go through all the plugins ?

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          1 Reply Last reply
          0
          • W Offline
            W Offline
            wesblake
            wrote on last edited by
            #5

            Not sure how to mark solved, but I figured it out going one by one. It wasn't the paths in the libraries, it turns out in 5.5 I also need QtDBus now. once I added that to the project and cleaned, everything works.

            1 Reply Last reply
            0
            • SGaistS Offline
              SGaistS Offline
              SGaist
              Lifetime Qt Champion
              wrote on last edited by
              #6

              What triggered the DBus dependency ?

              If the Topic Tools button doesn't allow that, then just edit the thread title prepending [solved] and your good

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              0

              • Login

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Users
              • Groups
              • Search
              • Get Qt Extensions
              • Unsolved