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. QtHelp include not found
Forum Updated to NodeBB v4.3 + New Features

QtHelp include not found

Scheduled Pinned Locked Moved General and Desktop
8 Posts 3 Posters 5.2k 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.
  • M Offline
    M Offline
    mirswith
    wrote on last edited by
    #1

    I am getting an error when I @#include <QtHelp>@

    error: @SomeFile.h:9: error: C1083: Cannot open include file: 'QtHelp': No such file or directory@

    My .pro file does contain @QT += help@ and I have also verified the QtHelp4.dll, QtHelp4.lib files exist and the QtHelp include folder exists.

    I have tried cleaning/rebuilding my project.

    Any ideas?

    Thanks.

    1 Reply Last reply
    0
    • V Offline
      V Offline
      vsorokin
      wrote on last edited by
      #2

      Check you qt include path, are /include/QtHelp/QtHelp file exists?
      If yes try:
      @#include <QtHelp/QtHelp>@

      --
      Vasiliy

      1 Reply Last reply
      0
      • M Offline
        M Offline
        mirswith
        wrote on last edited by
        #3

        That works. Why is QtHelp not in the same path as QtCore, QtGui, etc... ?

        Not a big deal now that its working for me but seems a bit strange.

        Thanks again! :)

        1 Reply Last reply
        0
        • L Offline
          L Offline
          lgeyer
          wrote on last edited by
          #4

          [quote author="mirswith" date="1318313471"]Why is QtHelp not in the same path as QtCore, QtGui, etc... ?[/quote]

          You should always use the module prefix and a specific element include.
          @
          #include <QtGui> // wrong, does include all gui elements
          #include <QPushButton> // wrong, does not use module prefix
          #include <QtGui/QPushButton> // right
          @

          1 Reply Last reply
          0
          • M Offline
            M Offline
            mirswith
            wrote on last edited by
            #5

            In that line of thinking should #include <QtHelp> not include all help includes. I do not see this as a 'wrong' way of thinking, the only downside is potential longer compile times vs. a potential large number of #include statements.

            1 Reply Last reply
            0
            • L Offline
              L Offline
              lgeyer
              wrote on last edited by
              #6

              Yes it should. The test feature is probably missing an INCLUDEPATH statement.

              "-Potential- Definitly longer compile times" is the difference between a coffee-break build and an overnight build (in terms of time and cost). Of course it isn't technically "wrong" - but not everything that is "not that wrong" is necessarily right ;-)

              1 Reply Last reply
              0
              • M Offline
                M Offline
                mirswith
                wrote on last edited by
                #7

                Is QtHelp a test feature? Docs say it was introduce in v4.4.

                1 Reply Last reply
                0
                • L Offline
                  L Offline
                  lgeyer
                  wrote on last edited by
                  #8

                  No. By feature I mean qmake "configuration features":http://doc.qt.nokia.com/stable/qmake-advanced-usage.html#adding-new-configuration-features found in $QTDIR/mkspecs/features.

                  I took a quick look at it and it looks like that the test feature is called testlib, not test. So it is either QT += testlib or CONFIG += test.

                  However, do yourself a favor and do not use module wide includes like #include <QtTest>. It is a bad habit and it will strike back at you and you will end up in fixing it somewhen.

                  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