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. [SOLVED] Autocomplete stopped in Qt Creator using SCons
Forum Updated to NodeBB v4.3 + New Features

[SOLVED] Autocomplete stopped in Qt Creator using SCons

Scheduled Pinned Locked Moved General and Desktop
12 Posts 3 Posters 5.9k 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.
  • S Offline
    S Offline
    sipickles
    wrote on last edited by
    #3

    Hi Andre,

    A pro file is archived, yes, but its not used at present. Since its a SCons build, we're just using the make style:

    *.files
    *.includes
    *.config

    I don't believe I can use a pro file too can I? Just to describe which modules - QtCore, QtGui, QtTest and QtNetwork in our case

    1 Reply Last reply
    0
    • A Offline
      A Offline
      andre
      wrote on last edited by
      #4

      QtCreator needs a build system it supports to know which modules are included, and of course which files are in the project. I think SCons is not one of the supported build sytems. AFAIK, only qmake, cmake and QBS (experimental) are supported.

      That makes it hard to work with Creator effectively in this case.

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

        Creator gets the include paths from the build system. -So did cmake detect Qt properly?- Which kind of project (and thus build system) are you using now? Does that detect Qt properly? If you are using a generic project: Did you set the relevant header paths and macros in the generic project configuration files?

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

          Andre: Actually there is autotools support as well, but that plugin is still marked as experimental.

          1 Reply Last reply
          0
          • A Offline
            A Offline
            andre
            wrote on last edited by
            #7

            [quote author="Tobias Hunger" date="1360915527"]Andre: Actually there is autotools support as well, but that plugin is still marked as experimental.[/quote]

            One learns something new every day :-)

            (not that I think autotools is a viable solution for a build system...)

            1 Reply Last reply
            0
            • S Offline
              S Offline
              sipickles
              wrote on last edited by
              #8

              Tobias, what did you mean by this ?

              Did you set the relevant header paths and macros in the generic project configuration files?

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

                Did you set up the generic project with the header paths and macros? There are files that creator reads to extract that information from. Check the documentation on generic projects for the details, I don't remember them right now.

                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  sipickles
                  wrote on last edited by
                  #10

                  Ok so solution was very easy. just add the Qt Include dirs to the myproject.includes file, eg:

                  @C:/Qt/4.8.3/include/QtCore
                  C:/Qt/4.8.3/include/QtGui
                  C:/Qt/4.8.3/include/QtTest
                  @

                  It all works! Qt types recognised and autocomplete restored. I was helped by this old page: http://cisharp.blogspot.co.uk/2009/08/qt-creator-tipps.html

                  The process is also described in the docs as Tobias says, which I had read but misunderstood:

                  http://doc.qt.digia.com/qtcreator-snapshot/creator-project-generic.html#specifying-include-paths

                  Thanks

                  1 Reply Last reply
                  0
                  • S Offline
                    S Offline
                    sipickles
                    wrote on last edited by
                    #11

                    Still seems daft having to tell Qt Creator about the Qt installation in this way.

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

                      sipickles: How is Creator supposed to extract that kind of information from a build system it does not understand at all? You could have configure that system to use something completely different from what you put into your kits. You may or may not use Qt at all in your project.

                      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