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. QFileSystemWatcher's signal "directoryChanged" not emitted
Forum Updated to NodeBB v4.3 + New Features

QFileSystemWatcher's signal "directoryChanged" not emitted

Scheduled Pinned Locked Moved Unsolved General and Desktop
qfilesystemwatcwindows10
43 Posts 5 Posters 21.3k Views 2 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 stephane78

    I have put

    INCLUDEPATH +="../../include"
    INCLUDEPATH +="../../include/QtCore"

    int he corelib.pro but I have an error In file included from ..\corelib\animation\qabstractanimation.cpp:143:0:
    ..\corelib\animation\qabstractanimation_p.h:52:31: fatal error: private/qobject_p.h: No such file or directory
    #include <private/qobject_p.h>

    S Offline
    S Offline
    stephane78
    wrote on last edited by
    #29

    It think I will build the whole Qtbase as usually and then open the corelib.pro and put the directory of lib QtCored.dll as build directory and try to debug with my exe (synchro.exe)

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #30

      You have to, qtbase, unlike the other modules, requires that you run configure before building it.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      S 2 Replies Last reply
      2
      • SGaistS SGaist

        You have to, qtbase, unlike the other modules, requires that you run configure before building it.

        S Offline
        S Offline
        stephane78
        wrote on last edited by
        #31

        @SGaist even after done configure,if I want to debug qtcore (corelib) in Qtcreator,it needs to be build with Qtcreator and I can't build it with Qtcreator (mingw).so I can't debug corelib (qtcore) and I don't know how to do.I have built qtbase with command line but it is unuseful...

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #32

          What problem do you get building from the command line ?

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          S 1 Reply Last reply
          0
          • SGaistS SGaist

            What problem do you get building from the command line ?

            S Offline
            S Offline
            stephane78
            wrote on last edited by stephane78
            #33

            @SGaist I have added INCLUDEPATH +="../../include"
            INCLUDEPATH +="../../include/QtCore"
            in the corelib.pro because I had errors on include paths but I have still errors on other include paths:
            In file included from C:\qtsrc\qtbase\src\corelib\animation\qabstractanimation.cpp:143:0:
            C:\qtsrc\qtbase\src\corelib\animation\qabstractanimation_p.h:52:31: fatal error: private/qobject_p.h: No such file or directory
            #include <private/qobject_p.h>
            ^

            S 1 Reply Last reply
            0
            • SGaistS Offline
              SGaistS Offline
              SGaist
              Lifetime Qt Champion
              wrote on last edited by
              #34

              You have to build qtbase from the command line. There's a lot of stuff happening during the build phase of qtbase like header generation. Therefore, build it once and then start hacking on it.

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              0
              • S stephane78

                @SGaist I have added INCLUDEPATH +="../../include"
                INCLUDEPATH +="../../include/QtCore"
                in the corelib.pro because I had errors on include paths but I have still errors on other include paths:
                In file included from C:\qtsrc\qtbase\src\corelib\animation\qabstractanimation.cpp:143:0:
                C:\qtsrc\qtbase\src\corelib\animation\qabstractanimation_p.h:52:31: fatal error: private/qobject_p.h: No such file or directory
                #include <private/qobject_p.h>
                ^

                S Offline
                S Offline
                stephane78
                wrote on last edited by
                #35

                @SGaist these problems are only for building with QTCreator.I have no problem to build with command line.but to debug QTCore in QTcreator I must build with QTcreator

                jsulmJ 1 Reply Last reply
                0
                • SGaistS SGaist

                  You have to, qtbase, unlike the other modules, requires that you run configure before building it.

                  S Offline
                  S Offline
                  stephane78
                  wrote on last edited by
                  #36

                  @SGaist I have built QTbase with command line without problem.But to debug QtCore with QtCreator I must build it with QtCreator.

                  1 Reply Last reply
                  0
                  • S stephane78

                    @SGaist these problems are only for building with QTCreator.I have no problem to build with command line.but to debug QTCore in QTcreator I must build with QTcreator

                    jsulmJ Offline
                    jsulmJ Offline
                    jsulm
                    Lifetime Qt Champion
                    wrote on last edited by
                    #37

                    @stephane78 Your assumption is wrong: you don't have to build with QtCreator to be able to debug in QtCreator. You just need to build a debug version.

                    https://forum.qt.io/topic/113070/qt-code-of-conduct

                    S 1 Reply Last reply
                    1
                    • jsulmJ jsulm

                      @stephane78 Your assumption is wrong: you don't have to build with QtCreator to be able to debug in QtCreator. You just need to build a debug version.

                      S Offline
                      S Offline
                      stephane78
                      wrote on last edited by
                      #38

                      @jsulm how to debug then ? I have a debug version of Qtbase and I have put the build directory where is the debug version but when I click on the debug button in Qtcreator it tries to build the project....

                      jsulmJ S 2 Replies Last reply
                      0
                      • S stephane78

                        @jsulm how to debug then ? I have a debug version of Qtbase and I have put the build directory where is the debug version but when I click on the debug button in Qtcreator it tries to build the project....

                        jsulmJ Offline
                        jsulmJ Offline
                        jsulm
                        Lifetime Qt Champion
                        wrote on last edited by
                        #39

                        @stephane78 To debug QtBase you need a project which is linked against it - you cannot execute a library, so you need an executable. Create a project write some code which uses QtBase, put a break point and start debugging. You then can step into QtBase code.

                        https://forum.qt.io/topic/113070/qt-code-of-conduct

                        1 Reply Last reply
                        0
                        • S stephane78

                          @jsulm how to debug then ? I have a debug version of Qtbase and I have put the build directory where is the debug version but when I click on the debug button in Qtcreator it tries to build the project....

                          S Offline
                          S Offline
                          stephane78
                          wrote on last edited by
                          #40

                          @jsulm ok jsuml you are right, I was not able to debug because shadow build was checked.I have unchecked it and now I can debug....so I am under windows 7.so I must try under windows 10 now and I come back when I have finished.......

                          S 1 Reply Last reply
                          0
                          • S stephane78

                            @jsulm ok jsuml you are right, I was not able to debug because shadow build was checked.I have unchecked it and now I can debug....so I am under windows 7.so I must try under windows 10 now and I come back when I have finished.......

                            S Offline
                            S Offline
                            stephane78
                            wrote on last edited by
                            #41

                            @jsulm yes I have an executable to debug qtcore,but my problem was only because shadow build was checked and it tries to build qtcore.now it is ok

                            S 1 Reply Last reply
                            0
                            • S stephane78

                              @jsulm yes I have an executable to debug qtcore,but my problem was only because shadow build was checked and it tries to build qtcore.now it is ok

                              S Offline
                              S Offline
                              stephane78
                              wrote on last edited by
                              #42

                              OK I have found a solution for windows to this bug (see :https://bugreports.qt.io/browse/QTBUG-59616). I have uploaded here the two files qfilesystemwatcher_win_p.h and qfilesystemwtacher_win.cpp that correct it.
                              I will search a solution for linux and for macos if there is the problem on mac os too....

                              S 1 Reply Last reply
                              0
                              • S stephane78

                                OK I have found a solution for windows to this bug (see :https://bugreports.qt.io/browse/QTBUG-59616). I have uploaded here the two files qfilesystemwatcher_win_p.h and qfilesystemwtacher_win.cpp that correct it.
                                I will search a solution for linux and for macos if there is the problem on mac os too....

                                S Offline
                                S Offline
                                stephane78
                                wrote on last edited by
                                #43

                                I have corrected this bug and the other under linux too, my correction is not very clean,but it corrects the bugs.I must look under mac os too

                                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