Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Deployment problem on MAC OSX with macdeployqt Qt5.4.2 (and 5.3.2)
Forum Updated to NodeBB v4.3 + New Features

Deployment problem on MAC OSX with macdeployqt Qt5.4.2 (and 5.3.2)

Scheduled Pinned Locked Moved Solved Installation and Deployment
35 Posts 2 Posters 13.2k Views 1 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.
  • S Offline
    S Offline
    stephane78
    wrote on last edited by
    #22

    I have tested without the other sql plugins and I have the same error...

    1 Reply Last reply
    0
    • S Offline
      S Offline
      stephane78
      wrote on last edited by
      #23

      The two MacOS on which that doesn't run are MacOS 10.9 and Mac OS 10.11.3 without Qt.
      But the software and bundle was made on a Mac OS 10.10.4.
      does the problem come from the MacOs version ?

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

        No it should not.

        Things I'd do now:

        1. Delete the bundle
        2. Do a full re-build
        3. Run macdeployqt on it
        4. Delete unused plugins
        5. Run otool -L on the remaining plugins
        6. Check whether there's any path to a non-system library that looks fishy
        7. Run otool -L on the application executable
        8. Check whether there's any path to a non-system library that looks fishy

        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
        1
        • S Offline
          S Offline
          stephane78
          wrote on last edited by
          #25

          already done several times the first three levels.
          an otool -L on the sqlite plugin gives paths to Qt libraries with "@rpath" but I suppose it 's ok.

          1 Reply Last reply
          0
          • S Offline
            S Offline
            stephane78
            wrote on last edited by stephane78
            #26

            and the sqlite plugin is linked with /usr/lib/libcc++.1.dylib and /usr/lib/libSystem.B.dylib too (and QtCore and QtSql)

            1 Reply Last reply
            0
            • S Offline
              S Offline
              stephane78
              wrote on last edited by
              #27

              I have build with Qt5.5.1 and I have the same problem than with Qt5.6.0

              1 Reply Last reply
              0
              • S Offline
                S Offline
                stephane78
                wrote on last edited by
                #28

                We will try later with a VM with MacOS 10.10 to see if it is a version problem

                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  stephane78
                  wrote on last edited by
                  #29

                  We have the same error on a MacOS 10.10 without the development environment (Qt,Xcode)

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

                    Might be a silly question but did you check all the plugins and the application itself for which version of Qt they are linked to ?

                    If everything looks correct, then I'd check the framework themselves to see if for any reasons one is not from the correct version.

                    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
                    • S Offline
                      S Offline
                      stephane78
                      wrote on last edited by
                      #31

                      @SGaist , Hi I have deleted Qt5.4.2 and Qt5.5.1 from the hard disk and built again the software with Qt5.6.0.
                      I have the same error on another Mac...

                      1 Reply Last reply
                      0
                      • S Offline
                        S Offline
                        stephane78
                        wrote on last edited by
                        #32

                        OK the problem is solved , iHave found the solution: our software use a config path (/Users/user/.config/software/) in which there are one database log file that is created.the config path did'nt exist, that was the explanation of this error.
                        the software is ok now,we create the path at the beginning if it doesn't exist.
                        I use Qt5.6.0 for this software (I think I could have used Qt5.5.1 too).

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

                          Haaaa that's a tricky one…

                          Indeed, the Qt version used wouldn't matter in this case.

                          So, if I understand you correctly, the database path was pointing to an invalid location ?

                          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
                          • S Offline
                            S Offline
                            stephane78
                            wrote on last edited by stephane78
                            #34

                            @SGaist, we should have created the path because the subdirectory .config didn't exist,so the software could not create and open the log database file.We have corrected that and now it runs well and the software is ok (we have created the path /.config/software in the user directory).
                            But for the first problem I had with macdeployqt, it doesn't run well with Qt 5.4, and it is ok with Qt5.6 (and perhaps with Qt5.5).as Qt5.6 is a long term support release I think Qt5.6 is a good choice

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

                              macdeployt has received several fixes since 5.4. Indeed 5.6 is a good choice from a support/maintenance point of view.

                              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