Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. [solved] Lost in Configuration ... Tool chains and their location
QtWS25 Last Chance

[solved] Lost in Configuration ... Tool chains and their location

Scheduled Pinned Locked Moved Qt Creator and other tools
6 Posts 3 Posters 4.5k 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.
  • S Offline
    S Offline
    secretNinja
    wrote on last edited by
    #1

    I'm using Windows 7 and the latest beta of QtCreator. I have problems setting the correct paths for the tool chains.

    I understand ( thank you Tobias Hunger ) that for GCCE I need:
    compiler - "C:\QtSDK\Symbian\tools\gcce4\bin\arm-none-symbianelf-g++.exe" and debugger - "C:\QtSDK\pythongdb\python_2.7based\gdb-arm-none-symbianelf.exe".

    But what about MinGW? Is this correct:
    compiler - "C:\QtSDK\mingw\bin\g++.exe" and debugger - "C:\QtSDK\mingw\bin\gdb.exe"?
    There is an error if I try to debug:

    bq. "The gdb installed at C:\QtSDK\mingw\bin\gdb.exe cannot find a valid python installation in its python.25 subdiectory. You may set the environment variable PYTHONPATH to point to your installation." .

    I added this variable but I wasn't sure where it should point to and then remove it.

    What is needed to be in my PATH in order the SDK to work the way it is supposed to? ( I think I messed with it badly ) It shouldn't be a problem that I have Microsoft Visual C++ Compiler auto-detected?

    I want to start writing code and stop fighting with the whole SDK ( and my stupidity ) :)

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tobias.hunger
      wrote on last edited by
      #2

      The compiler path is the complete path to the compilers exectuable (for Mingw/Gcc that is the gcc or g++ binary).

      The debugger is the complete path to the debugger executable. That is usually either cdb.exe for MSVC binaries or gdb.

      Qt Creator makes heavy use of the python support in newer versions of Gcc to produce human-readable output of many Qt datatypes. That seems to be missing in the gdb you have set up. Luckily we do ship known-to-be-good debuggers as part of Qt Creator in the pythongdb subdirectory of the Qt Creator installation (for embedded platforms as well as for 32bit mingw on windows).

      The Mingw that is configured as part of the Qt Creator installation will have the right settings, so just copy those.

      1 Reply Last reply
      0
      • S Offline
        S Offline
        secretNinja
        wrote on last edited by
        #3

        I have installed the latest snapshot ( again :) ) and now everything is working.
        Thank you :)

        1 Reply Last reply
        0
        • T Offline
          T Offline
          tobias.hunger
          wrote on last edited by
          #4

          We did fix a lot of bugs since the beta, working towards the RC release.

          1 Reply Last reply
          0
          • benlauB Offline
            benlauB Offline
            benlau
            Qt Champions 2016
            wrote on last edited by
            #5

            hmm... I have set to use the pythongdb , but it crash in launching. it just prompt a dailog and said "gdb is crashed". I have tried the gdb come with qtcreator 2.2 and 2010.05.01. Both are same. Any idea of the cause of problem?

            Thanks

            1 Reply Last reply
            0
            • T Offline
              T Offline
              tobias.hunger
              wrote on last edited by
              #6

              Please file a "bug report":http://bugreports.qt.nokia.com/ if something crashes!

              This is especially if you can provide good information on how to reproduce the issue and/or a backtrace. In case of a debugger issue the debugger log (top right in the debugger view) is absolutely necessary for us to find the issue, too, so please also include that.

              Looking forward to your report!

              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