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. Qt 5.4.0 iOS Code Signing Error while compiling (Qt Source)
Forum Updated to NodeBB v4.3 + New Features

Qt 5.4.0 iOS Code Signing Error while compiling (Qt Source)

Scheduled Pinned Locked Moved Installation and Deployment
5 Posts 2 Posters 2.3k 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.
  • B Offline
    B Offline
    berbande
    wrote on last edited by
    #1

    Hi,

    I hope someone can help me with this issue I have. I am trying to compile the Qt 5.4.0 Beta Source on a Mac OS X 10.9.4 with XCode 5.1.1 installed and I always get the same Build Error.

    I used this configuration:

    @./configure -opensource -xplatform macx-ios-clang -release -sdk iphoneos -nomake tools -nomake examples -nomake tests@

    I always end up with this error message while trying to 'make':

    @Check dependencies
    Code Sign error: No matching provisioning profiles found: No provisioning profiles with a valid signing identity (i.e. certificate and private key pair) were found.

    ** INSTALL FAILED **

    The following build commands failed:
    Check dependencies
    (1 failure)
    make[4]: *** [iphoneos-release-install] Error 65
    make[3]: *** [iphoneos-install] Error 2
    make[2]: *** [sub-xmlpatterns-install_subtargets] Error 2
    make[1]: *** [sub-tools-install_subtargets] Error 2
    make: *** [module-qtxmlpatterns-install_subtargets] Error 2@

    After searching I tried a lot, but the only information that helped me finishing 'make' was:

    http://qt-project.org/forums/viewthread/49420

    So I exported the developer identity and it successfully finished 'make'. Now I tried 'sudo make install' and it's stuck with the same error message you can see above. I also tried Qt 5.3.0 Source Release and Qt 5.4.0 Source Alpha but I always end up with the same error message.

    I appreciate any help.

    berbande

    1 Reply Last reply
    0
    • B Offline
      B Offline
      berbande
      wrote on last edited by
      #2

      Does someone has any idea why this error is showing up?

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

        Hi and welcome to devnet,

        Good question, I can currently only offer a workaround: install your custom built Qt in a path where you have write access.

        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
        • B Offline
          B Offline
          berbande
          wrote on last edited by
          #4

          Thank you SGaist. I have write access to the folder where Qt is located. The message appears about 3 to 4 minutes after the start of 'sudo make install' so i think if it has no write access this message would show up earlier.

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

            Then why are you calling make install with sudo if you already have write access to the folder where you want to install Qt ?

            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