Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Problem with Cross compiling
Forum Updated to NodeBB v4.3 + New Features

Problem with Cross compiling

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
10 Posts 4 Posters 3.6k 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.
  • H Offline
    H Offline
    Husky
    wrote on last edited by
    #1

    Hi Community,
    I want to Cross Compile from Windows 10 to Raspberry pi 3 with linux.
    Everything works fine, I can cross compile my Applications with QTCreator.
    But I have one Problem.
    If I add something to the Pro File. Then I get a warning:

    Warning: "C:\SysGCC\Raspberry\bin\arm-linux-gnueabihf-g++" is used by qmake, but "C:\SysGCC\Raspberry\bin\arm-linux-gnueabihf-g++.exe" is configured in the kit.
    Please update your kit or choose a mkspec for qmake that matches your target environment better.

    This gives me many Problems, so I can't add to qt += as example serialport.
    Or to config += lang-all ( for the virtual Keyboard).

    Cause in the Folder \SysGCC\Raspberry\bin\ there ist only arm-linux-gnueabihf-g++.exe in Windows.

    Do you have any suggestions?

    Best regards,
    Husky

    D 1 Reply Last reply
    0
    • sierdzioS Offline
      sierdzioS Offline
      sierdzio
      Moderators
      wrote on last edited by sierdzio
      #2

      Modify the mkspecs to point to the .exe. Or create a symlink without ".exe", I think new windowses do support such thing (not sure).

      (Z(:^

      H 1 Reply Last reply
      0
      • H Offline
        H Offline
        Husky
        wrote on last edited by
        #3
        This post is deleted!
        1 Reply Last reply
        0
        • sierdzioS sierdzio

          Modify the mkspecs to point to the .exe. Or create a symlink without ".exe", I think new windowses do support such thing (not sure).

          H Offline
          H Offline
          Husky
          wrote on last edited by
          #4

          @sierdzio Hi thanks for the answer. Is it possible to change the makespec after building?

          sierdzioS 1 Reply Last reply
          0
          • H Husky

            @sierdzio Hi thanks for the answer. Is it possible to change the makespec after building?

            sierdzioS Offline
            sierdzioS Offline
            sierdzio
            Moderators
            wrote on last edited by
            #5

            @Husky said in Problem with Cross compiling:

            @sierdzio Hi thanks for the answer. Is it possible to change the makespec after building?

            Well, kind of. If you change it after building, it will affect all future builds (of your application). It does not have any effect on Qt which you have already compiled. So if you had some compilation issues when comiling Qt, you need to adjust mkspecs and then recompile Qt.

            (Z(:^

            H 1 Reply Last reply
            0
            • sierdzioS sierdzio

              @Husky said in Problem with Cross compiling:

              @sierdzio Hi thanks for the answer. Is it possible to change the makespec after building?

              Well, kind of. If you change it after building, it will affect all future builds (of your application). It does not have any effect on Qt which you have already compiled. So if you had some compilation issues when comiling Qt, you need to adjust mkspecs and then recompile Qt.

              H Offline
              H Offline
              Husky
              wrote on last edited by
              #6

              @sierdzio So if I understand it right. I have to change the mkspec to ...gcc.exe instead of gcc. And then I have to recompile the whole qt on my target device?

              jsulmJ 1 Reply Last reply
              0
              • sierdzioS Offline
                sierdzioS Offline
                sierdzio
                Moderators
                wrote on last edited by
                #7

                Try without recompiling Qt first - it might be enough in your case to only update it to gcc.exe and recompile your application.

                (Z(:^

                1 Reply Last reply
                0
                • H Husky

                  @sierdzio So if I understand it right. I have to change the mkspec to ...gcc.exe instead of gcc. And then I have to recompile the whole qt on my target device?

                  jsulmJ Offline
                  jsulmJ Offline
                  jsulm
                  Lifetime Qt Champion
                  wrote on last edited by
                  #8

                  @Husky You could just rename gcc.exe in gcc (or copy gcc to gcc.exe) :-)

                  https://forum.qt.io/topic/113070/qt-code-of-conduct

                  1 Reply Last reply
                  0
                  • H Husky

                    Hi Community,
                    I want to Cross Compile from Windows 10 to Raspberry pi 3 with linux.
                    Everything works fine, I can cross compile my Applications with QTCreator.
                    But I have one Problem.
                    If I add something to the Pro File. Then I get a warning:

                    Warning: "C:\SysGCC\Raspberry\bin\arm-linux-gnueabihf-g++" is used by qmake, but "C:\SysGCC\Raspberry\bin\arm-linux-gnueabihf-g++.exe" is configured in the kit.
                    Please update your kit or choose a mkspec for qmake that matches your target environment better.

                    This gives me many Problems, so I can't add to qt += as example serialport.
                    Or to config += lang-all ( for the virtual Keyboard).

                    Cause in the Folder \SysGCC\Raspberry\bin\ there ist only arm-linux-gnueabihf-g++.exe in Windows.

                    Do you have any suggestions?

                    Best regards,
                    Husky

                    D Offline
                    D Offline
                    deleted184
                    wrote on last edited by
                    #9

                    HI @Husky ,

                    I assume you did, but did you use the same compiler to build your qmake (QMAKE_XSPEC value in the Qt Version detail) that the one you use to configure your Kit ?

                    If it helps this is my confguration :

                    https://pasteboard.co/1oTFoCeh3.png

                    1 Reply Last reply
                    0
                    • H Offline
                      H Offline
                      Husky
                      wrote on last edited by Husky
                      #10

                      Hi thanks to all.
                      Sry for my late reply, I wasn't at home the last week.

                      https://forum.qt.io/topic/68381/cross-compile-qt-windows-to-raspberry-3

                      I use this instruction to build my toolchain.
                      But I have this problem and didn't get it worked corecctly.
                      I tried to rename but it doesn't work. Have someone an instruction how I can change, the mkspec. To the last reply my settings are the same as yours only that by xspec I have /device/rpi3-g++.

                      I have absolutly no idea why I get this warning. I can compile my Applications without Problems. But if I add something to CONFIG=+ it doesn't work.

                      Best regards, Husky

                      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