Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Special Interest Groups
  3. Qt on BlackBerry and QNX
  4. Toolchain issue: Missing mkspecs
Forum Updated to NodeBB v4.3 + New Features

Toolchain issue: Missing mkspecs

Scheduled Pinned Locked Moved Qt on BlackBerry and QNX
9 Posts 3 Posters 6.0k 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.
  • C Offline
    C Offline
    codenode
    wrote on last edited by
    #1

    I've installed the BBNDK in my Linux VM, and when starting the IDE and compiling a first project, I get this error:

    ErrorMessage:
    Could not find mkspecs for your QMAKESPECS(unsupported/blackberry-arm7le-qcc) after trying:
    /home/jw/bbndk/target_10_0_9_386/usr/share/qt4/mkspecs

    Looking into the NDK, the path above only exists as far as usr/. There is no share, hence no mkspecs.
    I've looked into the installer log, and could not find any error, so how to fix this?

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

      Hi,
      The path should actually be there...but currently no default mkspecs are set. This will change in the next NDK version.
      Your NDK installation might be not completed because there definitively are mkspecs. COuld you try installing it again?

      1 Reply Last reply
      0
      • C Offline
        C Offline
        Coldpeace
        wrote on last edited by
        #3

        Hi,

        The default mkspec is missing on the current Alpha3 NDK.
        If you want to compile for the Simulator you need to explicitly specify the mkspec to use:

        unsupported/blackberry-x86-qcc

        If you're using QtCreator QNX plugin, you can specify the mkspec in the Kit you're using ( last parameter).

        Otherwise, you can just create a sym link to the mkpec you wanna use :

        cd $PATH_TO/usr/share/qt4/mkspecs
        ln -s unsupported/blackberry-x86-qcc default

        1 Reply Last reply
        0
        • C Offline
          C Offline
          Coldpeace
          wrote on last edited by
          #4

          If you compile for the device link to unsupported/blackberry-armv7le-qcc

          1 Reply Last reply
          0
          • C Offline
            C Offline
            codenode
            wrote on last edited by
            #5

            [quote author="Coldpeace" date="1350044303"]Hi,

            The default mkspec is missing on the current Alpha3 NDK.
            If you want to compile for the Simulator you need to explicitly specify the mkspec to use:

            unsupported/blackberry-x86-qcc

            [/quote]

            I'm currently using the BBNDK IDE. Where to find the correct mkspecs?

            1 Reply Last reply
            0
            • C Offline
              C Offline
              codenode
              wrote on last edited by
              #6

              Looking into a different VM, I see that those files seem not to be installed right. So, I'll try to fix that.

              So, copied from another installation the qnx6 folder, which brings a bit more errors, but also solves this one.
              Seems like that the installer has screwed up here, reinstalling new NDK...

              1 Reply Last reply
              0
              • C Offline
                C Offline
                Coldpeace
                wrote on last edited by
                #7

                use find command to locate it:

                find /home/jw/bbndk/ -name blackberry-x86-qcc (or blackberry-armv7le-qcc if device target)

                The mkspecs should be located under your:

                /home/jw/bbndk/target_10_0_9_386/qnx6/usr/share/qt4/mkspecs on linux (isn't?)
                (under "unsupported" dir)

                Then you just need to add a default sym link as I posted before.

                Are you compiling a Cascade projects or pure Qt Project?

                1 Reply Last reply
                0
                • C Offline
                  C Offline
                  codenode
                  wrote on last edited by
                  #8

                  So, reinstalled, and it works.

                  Coldpeace:
                  that part was missing in my installation.
                  Reinstallment solved it...

                  1 Reply Last reply
                  0
                  • C Offline
                    C Offline
                    Coldpeace
                    wrote on last edited by
                    #9

                    Nice! :)

                    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