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. Makefile project and precompiled headers

Makefile project and precompiled headers

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
4 Posts 2 Posters 1.3k 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.
  • E Offline
    E Offline
    Esperantisto
    wrote on last edited by Esperantisto
    #1

    I have an external project that I have imported into qtcreator ("Import Existing Project"). This external project uses precompiled headers. The precompiled header file is not included in any of the project's header files, so when I edit those files in qtcreator, I don't get tooltips, code completion or correct highlighting.

    Is there a way to tell qtcreator what the precompiled header is for parsing purposes, perhaps through the .creator or .config files?

    JohanSoloJ 1 Reply Last reply
    0
    • E Esperantisto

      I have an external project that I have imported into qtcreator ("Import Existing Project"). This external project uses precompiled headers. The precompiled header file is not included in any of the project's header files, so when I edit those files in qtcreator, I don't get tooltips, code completion or correct highlighting.

      Is there a way to tell qtcreator what the precompiled header is for parsing purposes, perhaps through the .creator or .config files?

      JohanSoloJ Offline
      JohanSoloJ Offline
      JohanSolo
      wrote on last edited by
      #2

      @Esperantisto said:

      Is there a way to tell qtcreator what the precompiled header is for parsing purposes, perhaps through the .creator or .config files?

      Sure, you can use the <projectname>.includes file and add the additional include paths.

      `They did not know it was impossible, so they did it.'
      -- Mark Twain

      1 Reply Last reply
      0
      • E Offline
        E Offline
        Esperantisto
        wrote on last edited by
        #3

        That doesn't tell the parser which files are being included.

        1 Reply Last reply
        0
        • JohanSoloJ Offline
          JohanSoloJ Offline
          JohanSolo
          wrote on last edited by
          #4

          @Esperantisto said:

          That doesn't tell the parser which files are being included.

          Well, it definitely does for me... I regularly create project from pre-existing makefiles which are in a folder directory different from the sources. Are you talking about the sources of the project? In that case use the <projectname>.files file. But the included files are loaded from the various includes location defined in the <projectname>.includes, and the help / documentation and signatures are loaded from there as well.

          `They did not know it was impossible, so they did it.'
          -- Mark Twain

          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