QFileSystemWatcher's signal "directoryChanged" not emitted
-
@VRonin OK I think I have found : I have copied the directory include of the source single (.zip) of 5.6.2 in the direcorty qtbase and I have put in my environment variable INCLUDE the path of directory include and reboot my windows...I think it will be ok
wrote on 24 Mar 2017, 16:01 last edited byI 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> -
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>wrote on 24 Mar 2017, 16:25 last edited byIt 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)
-
You have to, qtbase, unlike the other modules, requires that you run configure before building it.
-
You have to, qtbase, unlike the other modules, requires that you run configure before building it.
wrote on 27 Mar 2017, 08:17 last edited by@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...
-
What problem do you get building from the command line ?
-
wrote on 27 Mar 2017, 10:08 last edited by 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>
^ -
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.
-
@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>
^wrote on 27 Mar 2017, 10:15 last edited by@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
-
You have to, qtbase, unlike the other modules, requires that you run configure before building it.
wrote on 27 Mar 2017, 10:19 last edited by@SGaist I have built QTbase with command line without problem.But to debug QtCore with QtCreator I must build it with QtCreator.
-
@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
@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.
-
@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.
wrote on 27 Mar 2017, 12:20 last edited by@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....
-
@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....
@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.
-
@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....
wrote on 27 Mar 2017, 12:31 last edited by -
wrote on 27 Mar 2017, 12:36 last edited by
@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
-
@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
wrote on 29 Mar 2017, 10:44 last edited byOK 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.... -
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....wrote on 3 Apr 2017, 07:29 last edited byI 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
37/43