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. Mingw32 undefined reference
Forum Updated to NodeBB v4.3 + New Features

Mingw32 undefined reference

Scheduled Pinned Locked Moved Solved General and Desktop
41 Posts 6 Posters 8.4k Views
  • 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.
  • D Offline
    D Offline
    Dre4m
    wrote on last edited by
    #30

    0_1551267433870_14ed7be9-747a-4534-a73b-04f1079c6237-obraz.png

    here you go

    aha_1980A 1 Reply Last reply
    0
    • D Dre4m

      0_1551267433870_14ed7be9-747a-4534-a73b-04f1079c6237-obraz.png

      here you go

      aha_1980A Offline
      aha_1980A Offline
      aha_1980
      Lifetime Qt Champion
      wrote on last edited by
      #31

      @Dre4m

      How did the c:\Qt\%VERSION%\bin entry get there?

      Qt has to stay free or it will die.

      1 Reply Last reply
      0
      • D Offline
        D Offline
        Dre4m
        wrote on last edited by
        #32

        i've added it today manually while tried to fix the problem

        KroMignonK 1 Reply Last reply
        0
        • D Dre4m

          i've added it today manually while tried to fix the problem

          KroMignonK Offline
          KroMignonK Offline
          KroMignon
          wrote on last edited by
          #33

          @Dre4m is VERSION defined?

          It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

          D 1 Reply Last reply
          1
          • KroMignonK KroMignon

            @Dre4m is VERSION defined?

            D Offline
            D Offline
            Dre4m
            wrote on last edited by
            #34

            @KroMignon to be honest i have no idea , i've just followed some instruction anyway i have deleted it and my PAth looks like that now
            0_1551269396195_4ef0c62e-13f7-460a-8f66-cc4337dab173-obraz.png

            jsulmJ 1 Reply Last reply
            0
            • D Dre4m

              @KroMignon to be honest i have no idea , i've just followed some instruction anyway i have deleted it and my PAth looks like that now
              0_1551269396195_4ef0c62e-13f7-460a-8f66-cc4337dab173-obraz.png

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

              @Dre4m Log out and login from Windows, delete build directory, run qmake and build

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

              1 Reply Last reply
              1
              • D Offline
                D Offline
                Dre4m
                wrote on last edited by Dre4m
                #36

                nope same result

                E 1 Reply Last reply
                0
                • D Dre4m

                  nope same result

                  E Offline
                  E Offline
                  etla
                  wrote on last edited by etla
                  #37

                  @Dre4m I had a similar problem but the opposite; I had both 64 and 32 bit tool kits installed in parallel and by some reason Qt Creator got all messed up and tried to run the 32 bit version of gdb on my 64 bit compiled binaries and there were no way of changing that in the settings (the gdb-field was greyed out). Hilarity Ensues. Nothing compiled and the log output made absolutely no sense.

                  The solution for me was to clean up my environment to run only ONE setup of tools, ie the 64 bit MinGW. I'd suggest you start with removing the 5.12.1-kit and install the full 5.11.3-kit instead. Also check that there isn't a lot of stuff added under "Developer and Designer Tools", I only have "Qt Creator 4.8.1" and "MinGW 7.3.0 64-bit" checked there (and I guess you should have "MinGW 5.30 32-bit" checked instead).

                  Code in haste; debug in leisure.

                  1 Reply Last reply
                  2
                  • D Offline
                    D Offline
                    Dre4m
                    wrote on last edited by
                    #38

                    will try in home on clean installation of qt

                    E 1 Reply Last reply
                    1
                    • D Dre4m

                      will try in home on clean installation of qt

                      E Offline
                      E Offline
                      etla
                      wrote on last edited by
                      #39

                      @Dre4m There's another weird behavior I noticed when I tried to reinstall Qt Creator. Apparently the kits doesn't get properly set up if you do it at install time, so just install a bare bone Qt Creator first and add the kit afterwards is my tip. At least that was what I had to do to get all bindings etc right.

                      Dunno why. Now it works so I don't mess with it in fear that things will break again.

                      Code in haste; debug in leisure.

                      1 Reply Last reply
                      1
                      • D Offline
                        D Offline
                        Dre4m
                        wrote on last edited by
                        #40

                        Still i dont understand why 64 bit version installed correctly and 32 didnt

                        1 Reply Last reply
                        0
                        • D Offline
                          D Offline
                          Dre4m
                          wrote on last edited by
                          #41

                          To any interested person , i've figured out that somehow linker when building project was using mings64 bit path and didn't see refferences so i changed manually folder name of mingw 64 bit and somehow qt decided that its time to use PATH of 32-bit version of mingw , then i changed again name of folder back to normall and now its working on 32 bit version and 64 bit version.

                          1 Reply Last reply
                          1

                          • Login

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