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. #include repost
Forum Updated to NodeBB v4.3 + New Features

#include repost

Scheduled Pinned Locked Moved Unsolved General and Desktop
22 Posts 7 Posters 1.2k Views 3 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.
  • A Offline
    A Offline
    Anonymous_Banned275
    wrote on last edited by
    #1

    Since my original post DID NOT get solved I am taking the liberty t repost with additional info.
    I am trying not to reinvent the wheel and putting two WORKING application under one roof.
    My task is to add existing files of btscanner apprication into tab dialog.

    I am using plain "add existing files " and they are being added into correct folders under correct additional sub folders showing the path.

    c43a0711-86c3-4094-88f4-42a9c98b3785-image.png

    They are added into tab dialog project

    d4cb4299-7702-4a33-93cf-b6eb1cd43140-image.png

    I have added this manually

    b6890c61-0812-4c42-ba9b-949960e6fe61-image.png

    After all this - complier cannot find #inlcude - starting wiht "main.cpp"

    ffbf71af-851c-4154-ae03-6fdc14294ee3-image.png

    763ee4a5-98a6-4928-a96f-87335df90d72-image.png

    14a2b03d-518c-4f24-babc-334c59227aee-image.png

    Missing device.h in main error

    3303c144-9d55-4df5-9d85-d4ba3a0044a9-image.png

    Questions

    1. What do additional folders with path accomplish ?
    2. How do x.pro HEADERS gets used or not ge used by whom - makefile or compiler?
    3. It looks as plain "include device.h" in source file is not sufficient to make / compile - WHERE DO I ADD the necessryn path ?

    Addendum
    After adding relative path to #include it passed device but not service header. .

    966d9869-1dcc-4978-8142-724831afe7b7-image.png

    Cheers

    Pl45m4P 1 Reply Last reply
    0
    • hskoglundH Offline
      hskoglundH Offline
      hskoglund
      wrote on last edited by
      #2

      Hi, shouldn't it be #include ..../service.h (not sevice.h)?

      1 Reply Last reply
      1
      • A Offline
        A Offline
        Anonymous_Banned275
        wrote on last edited by
        #3

        #include " file " ; searches local directory ONLY and stops
        #include <file> ; searches "above " local directory

        The "../../.." syntax seems to go "up the tree" , assuming the referenced project is in "current access". (I need to work on that theory)

        Anything else , such as ellipsis or "....." is unknown syntax to me.
        Can you provide reference ?

        B 1 Reply Last reply
        0
        • hskoglundH Offline
          hskoglundH Offline
          hskoglund
          wrote on last edited by
          #4

          Sorry, I mean, the line no. 45 that currently has the red error is:

          #include <../../bluetooth/btscanner/sevice.h>
          

          try changing it to:

          #include <../../bluetooth/btscanner/service.h>
          
          1 Reply Last reply
          2
          • A Anonymous_Banned275

            #include " file " ; searches local directory ONLY and stops
            #include <file> ; searches "above " local directory

            The "../../.." syntax seems to go "up the tree" , assuming the referenced project is in "current access". (I need to work on that theory)

            Anything else , such as ellipsis or "....." is unknown syntax to me.
            Can you provide reference ?

            B Offline
            B Offline
            Bonnie
            wrote on last edited by
            #5

            @AnneRanch
            I think @hskoglund means you've made a typo...

            A 2 Replies Last reply
            3
            • A Offline
              A Offline
              Anonymous_Banned275
              wrote on last edited by
              #6

              Here is what works partial path (?) and then full path - the entire project compiles and runs.

              6f633b57-2455-405b-8239-78d2dcddf217-image.png

              Anybody interested to find out WHY it works ?
              Perhaps detailed analysis of complier output - now available AFTER the error is gone (!) would be interesting to somebody. ( I could post it)

              My "solution" is
              path (GUI) in "project tree" and (../../..) in x.pro file means NOTHING to the complier.

              1 Reply Last reply
              0
              • A Anonymous_Banned275

                Since my original post DID NOT get solved I am taking the liberty t repost with additional info.
                I am trying not to reinvent the wheel and putting two WORKING application under one roof.
                My task is to add existing files of btscanner apprication into tab dialog.

                I am using plain "add existing files " and they are being added into correct folders under correct additional sub folders showing the path.

                c43a0711-86c3-4094-88f4-42a9c98b3785-image.png

                They are added into tab dialog project

                d4cb4299-7702-4a33-93cf-b6eb1cd43140-image.png

                I have added this manually

                b6890c61-0812-4c42-ba9b-949960e6fe61-image.png

                After all this - complier cannot find #inlcude - starting wiht "main.cpp"

                ffbf71af-851c-4154-ae03-6fdc14294ee3-image.png

                763ee4a5-98a6-4928-a96f-87335df90d72-image.png

                14a2b03d-518c-4f24-babc-334c59227aee-image.png

                Missing device.h in main error

                3303c144-9d55-4df5-9d85-d4ba3a0044a9-image.png

                Questions

                1. What do additional folders with path accomplish ?
                2. How do x.pro HEADERS gets used or not ge used by whom - makefile or compiler?
                3. It looks as plain "include device.h" in source file is not sufficient to make / compile - WHERE DO I ADD the necessryn path ?

                Addendum
                After adding relative path to #include it passed device but not service header. .

                966d9869-1dcc-4978-8142-724831afe7b7-image.png

                Cheers

                Pl45m4P Online
                Pl45m4P Online
                Pl45m4
                wrote on last edited by
                #7

                @AnneRanch said in #include repost:

                I have added this manually

                Just to add:
                This is pure evil :)
                Dont use = to change settings... Use += to add modules to your basic config or use -= to take modules.

                https://doc.qt.io/qt-5/qmake-project-files.html#declaring-qt-libraries


                If debugging is the process of removing software bugs, then programming must be the process of putting them in.

                ~E. W. Dijkstra

                1 Reply Last reply
                3
                • A Offline
                  A Offline
                  Anonymous_Banned275
                  wrote on last edited by
                  #8

                  Minor , insignificant detail not helping to resolve THIS #include issue.
                  BTW - I just cut and pasted it from "an official" btscanner example .

                  Pl45m4P 1 Reply Last reply
                  -2
                  • B Bonnie

                    @AnneRanch
                    I think @hskoglund means you've made a typo...

                    A Offline
                    A Offline
                    Anonymous_Banned275
                    wrote on last edited by
                    #9
                    This post is deleted!
                    1 Reply Last reply
                    0
                    • B Bonnie

                      @AnneRanch
                      I think @hskoglund means you've made a typo...

                      A Offline
                      A Offline
                      Anonymous_Banned275
                      wrote on last edited by
                      #10

                      @Bonnie Mia culpa - I DID MADE a typo

                      J.HilkJ 1 Reply Last reply
                      0
                      • A Anonymous_Banned275

                        Minor , insignificant detail not helping to resolve THIS #include issue.
                        BTW - I just cut and pasted it from "an official" btscanner example .

                        Pl45m4P Online
                        Pl45m4P Online
                        Pl45m4
                        wrote on last edited by Pl45m4
                        #11

                        @AnneRanch

                        It's a general thing.
                        As I've said in one of your other posts, examples are minimalistic standalone projects, that are (in most cases) not meant to get improved or extended even further.
                        So, IMHO it's not a good idea to import a whole example to your own projects and take over the example's pro file...
                        I don't want to question your whole idea, but I would say, that there are easier and faster ways to make your own BT Scanner "test" / "example" project.
                        Or is there anything that forces you, to import the full example?


                        If debugging is the process of removing software bugs, then programming must be the process of putting them in.

                        ~E. W. Dijkstra

                        A 1 Reply Last reply
                        0
                        • A Anonymous_Banned275

                          @Bonnie Mia culpa - I DID MADE a typo

                          J.HilkJ Offline
                          J.HilkJ Offline
                          J.Hilk
                          Moderators
                          wrote on last edited by J.Hilk
                          #12

                          @AnneRanch to answer your original question, the pro- file offers you the possibility to expand the include path, via INCLUDPATH += ....

                          in your case

                          INCLUDEPATH +=$$PWD/../../bluetooth/btscanner
                          

                          should do the trick.

                          But use it with caution, I find that using INCLUDEPATH convolutes the code more than that it makes it easier to read.
                          But that maybe just me

                          #include " file " ; searches local directory ONLY and stops
                          #include <file> ; searches "above " local directory

                          where did you get that from?

                          the actual definition:

                          1. #include <filename>: Searches for the file in implementation-defined manner. The intent of this syntax is to search for the files under control of the implementation. Typical implementations search only standard include directories. The standard C++ library and the standard C library are implicitly included in these standard include directories. The standard include directories usually can be controlled by the user through compiler options.
                          2. #include "filename": Searches for the file in implementation-defined manner. The intent of this syntax is to search for the files that are not controlled by the implementation. Typical implementations first search the directory where the current file resides and, only if the file is not found, search the standard include directories as with (1).

                          https://en.cppreference.com/w/cpp/preprocessor/include

                          The only thing that "searches upward" that I now, is qmake in search of a .qmake.conf file
                          But there may be more 🤷‍♂️


                          Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


                          Q: What's that?
                          A: It's blue light.
                          Q: What does it do?
                          A: It turns blue.

                          A 1 Reply Last reply
                          5
                          • Pl45m4P Pl45m4

                            @AnneRanch

                            It's a general thing.
                            As I've said in one of your other posts, examples are minimalistic standalone projects, that are (in most cases) not meant to get improved or extended even further.
                            So, IMHO it's not a good idea to import a whole example to your own projects and take over the example's pro file...
                            I don't want to question your whole idea, but I would say, that there are easier and faster ways to make your own BT Scanner "test" / "example" project.
                            Or is there anything that forces you, to import the full example?

                            A Offline
                            A Offline
                            Anonymous_Banned275
                            wrote on last edited by
                            #13

                            @Pl45m4 Agree with your approach, however, the initial question was about why "#include" does not work as expected AND
                            why the project tree and project file entries make no difference OR more precisely does not effect the complication. My usage of btscanner is purely selfish – it works in Qt - as opposed to many other “sample codes” , and that is OK with me.

                            What is NOT OK is tool likes Qt Creator messing with C language syntax by adding layers of
                            poorly explained “STUFF” , such as inventing syntax “/../../xxx” where #include <FILIE>; should do.

                            As far as “samples” being second grade code – something about advertising Qt comes to mind, and I shall leave that as is.

                            JonBJ 1 Reply Last reply
                            0
                            • J.HilkJ J.Hilk

                              @AnneRanch to answer your original question, the pro- file offers you the possibility to expand the include path, via INCLUDPATH += ....

                              in your case

                              INCLUDEPATH +=$$PWD/../../bluetooth/btscanner
                              

                              should do the trick.

                              But use it with caution, I find that using INCLUDEPATH convolutes the code more than that it makes it easier to read.
                              But that maybe just me

                              #include " file " ; searches local directory ONLY and stops
                              #include <file> ; searches "above " local directory

                              where did you get that from?

                              the actual definition:

                              1. #include <filename>: Searches for the file in implementation-defined manner. The intent of this syntax is to search for the files under control of the implementation. Typical implementations search only standard include directories. The standard C++ library and the standard C library are implicitly included in these standard include directories. The standard include directories usually can be controlled by the user through compiler options.
                              2. #include "filename": Searches for the file in implementation-defined manner. The intent of this syntax is to search for the files that are not controlled by the implementation. Typical implementations first search the directory where the current file resides and, only if the file is not found, search the standard include directories as with (1).

                              https://en.cppreference.com/w/cpp/preprocessor/include

                              The only thing that "searches upward" that I now, is qmake in search of a .qmake.conf file
                              But there may be more 🤷‍♂️

                              A Offline
                              A Offline
                              Anonymous_Banned275
                              wrote on last edited by
                              #14

                              @J-Hilk
                              I will repeat what I have said already and add - the syntax for #inlcude has not changed since it was introduced. The Qt Creator adds stuff which is not only odd but is not used during compile.
                              Yes, I did not cut and paste "the real Mc Coy" definition as you did.
                              Was MY definition incorrect ?
                              I am not sure if adding PATH (to pro file) is necessary - it is already in project tree and if it is important it should be added to pro file by Qt Creator.

                              Appreciate all the comments and suggestions, it is very helpful to get my project going.

                              Thanks

                              1 Reply Last reply
                              0
                              • A Anonymous_Banned275

                                @Pl45m4 Agree with your approach, however, the initial question was about why "#include" does not work as expected AND
                                why the project tree and project file entries make no difference OR more precisely does not effect the complication. My usage of btscanner is purely selfish – it works in Qt - as opposed to many other “sample codes” , and that is OK with me.

                                What is NOT OK is tool likes Qt Creator messing with C language syntax by adding layers of
                                poorly explained “STUFF” , such as inventing syntax “/../../xxx” where #include <FILIE>; should do.

                                As far as “samples” being second grade code – something about advertising Qt comes to mind, and I shall leave that as is.

                                JonBJ Offline
                                JonBJ Offline
                                JonB
                                wrote on last edited by JonB
                                #15

                                @AnneRanch said in #include repost:

                                What is NOT OK is tool likes Qt Creator messing with C language syntax by adding layers of
                                poorly explained “STUFF” , such as inventing syntax “/../../xxx” where #include <FILIE>; should do.

                                Qt Creator is an IDE, including a C/C++ editor and a debugger. It does not, and cannot, alter the syntax of any language. If it did, programs would not compile. The compiler/linker is not a Qt component.

                                Whatever #includes you have shown in your code will conform to https://en.cppreference.com/w/cpp/preprocessor/include, or similar, as per @J-Hilk 's post. Assuming your are using gcc, its documentation should provide any details on handling/how to pass directories on the compile line, etc. #include <> tends to look in some system directories which #include "" does not. Handling of a relative path with .. is probably compiler-implementation-specific.

                                A 1 Reply Last reply
                                3
                                • JonBJ JonB

                                  @AnneRanch said in #include repost:

                                  What is NOT OK is tool likes Qt Creator messing with C language syntax by adding layers of
                                  poorly explained “STUFF” , such as inventing syntax “/../../xxx” where #include <FILIE>; should do.

                                  Qt Creator is an IDE, including a C/C++ editor and a debugger. It does not, and cannot, alter the syntax of any language. If it did, programs would not compile. The compiler/linker is not a Qt component.

                                  Whatever #includes you have shown in your code will conform to https://en.cppreference.com/w/cpp/preprocessor/include, or similar, as per @J-Hilk 's post. Assuming your are using gcc, its documentation should provide any details on handling/how to pass directories on the compile line, etc. #include <> tends to look in some system directories which #include "" does not. Handling of a relative path with .. is probably compiler-implementation-specific.

                                  A Offline
                                  A Offline
                                  Anonymous_Banned275
                                  wrote on last edited by
                                  #16

                                  @JonB This comments i misinterpreters this entire thread.
                                  Nobody is challenging Qt as IDE "interface " to make and compiler / linker.
                                  What I questioned is what appears superficial "includes" with no visible effect on processes. If common item likes #include has to be done manually we have very poorly functioning "IDE", nothing to do with complier.

                                  Since you mentioned complier - where can I read Qt Creator compile options ?
                                  I have 4 processor system and like to add "-j" option to speed things up.

                                  But I'll post this separately - different subject

                                  JonBJ Pl45m4P 2 Replies Last reply
                                  0
                                  • A Anonymous_Banned275

                                    @JonB This comments i misinterpreters this entire thread.
                                    Nobody is challenging Qt as IDE "interface " to make and compiler / linker.
                                    What I questioned is what appears superficial "includes" with no visible effect on processes. If common item likes #include has to be done manually we have very poorly functioning "IDE", nothing to do with complier.

                                    Since you mentioned complier - where can I read Qt Creator compile options ?
                                    I have 4 processor system and like to add "-j" option to speed things up.

                                    But I'll post this separately - different subject

                                    JonBJ Offline
                                    JonBJ Offline
                                    JonB
                                    wrote on last edited by
                                    #17

                                    @AnneRanch said in #include repost:

                                    @JonB This comments i misinterpreters this entire thread.

                                    No, it doesn't. You think that Qt Creator is doing something funny about #includes, and keep saying so. It is not.

                                    1 Reply Last reply
                                    1
                                    • A Anonymous_Banned275

                                      @JonB This comments i misinterpreters this entire thread.
                                      Nobody is challenging Qt as IDE "interface " to make and compiler / linker.
                                      What I questioned is what appears superficial "includes" with no visible effect on processes. If common item likes #include has to be done manually we have very poorly functioning "IDE", nothing to do with complier.

                                      Since you mentioned complier - where can I read Qt Creator compile options ?
                                      I have 4 processor system and like to add "-j" option to speed things up.

                                      But I'll post this separately - different subject

                                      Pl45m4P Online
                                      Pl45m4P Online
                                      Pl45m4
                                      wrote on last edited by Pl45m4
                                      #18

                                      @AnneRanch said in #include repost:

                                      I have 4 processor system and like to add "-j" option to speed things up.

                                      https://stackoverflow.com/questions/8860712/setting-default-make-options-for-qt-creator

                                      (4 processor cores, I assume)


                                      If debugging is the process of removing software bugs, then programming must be the process of putting them in.

                                      ~E. W. Dijkstra

                                      A 1 Reply Last reply
                                      0
                                      • A Offline
                                        A Offline
                                        Anonymous_Banned275
                                        wrote on last edited by
                                        #19
                                        This post is deleted!
                                        1 Reply Last reply
                                        0
                                        • Pl45m4P Pl45m4

                                          @AnneRanch said in #include repost:

                                          I have 4 processor system and like to add "-j" option to speed things up.

                                          https://stackoverflow.com/questions/8860712/setting-default-make-options-for-qt-creator

                                          (4 processor cores, I assume)

                                          A Offline
                                          A Offline
                                          Anonymous_Banned275
                                          wrote on last edited by
                                          #20

                                          @Pl45m4 Pardon my ignorance , but -j is a complier option .
                                          When I added it to "make" it did not show in compiler output.
                                          Which brings another question - who is on first - "make" or "qmake" or both ?
                                          And since I am not allowed to do multiple posts - why is there "build" and "rebuild" ? Back in the beginning of programming - when file was "dirty" it would get rebuild AUTOMATICALLY when "build" was requested anyway.
                                          .

                                          Pl45m4P JKSHJ 2 Replies 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