Dependent (that clearly exists) does not exist error when building Qt Creator project
-
Uhm... seems to be a bigger one. You will need to search the
.prifiles forrouter_app_service_interface.hppand see if that gives you new insight.Resolving that might be a challenging task - not sure if forum support is sufficient for that.
Regards
-
@aha_1980 That makes sense - I'll look into it, and for the record the antivirus/admin windows settings on my laptop are fairly strict because of company policies, any chance that could be causing issues?
@jacobdbernard said in Dependent (that clearly exists) does not exist error when building Qt Creator project:
and for the record the antivirus/admin windows settings on my laptop are fairly strict because of company policies, any chance that could be causing issues?
Yeah, these are always a source for fun. However, in your case I doubt it.
What you can also do is to inspect the generated Makefile. We already know it is wrong, but maybe you see why it is wrong.
Good luck!
-
Hi,
@jacobdbernard said in Dependent (that clearly exists) does not exist error when building Qt Creator project:
object_parallel_to_source
I wonder if this one might be part of the problem.
-
@SGaist I see what you mean looking at the documentation, but unfortunately removing that option didn't seem to make a difference.
-
I have the same exact error on Windows 10 with Qt 5.12.3, but not on macOS 10.14.4 with same Qt version. I did not get this error on Windows 10 with Qt 5.5.1.
I tried all the ideas above so this seems to be a bug in Qt 5.12.3 for Windows. Have you found any solution?
-
I have the same exact error on Windows 10 with Qt 5.12.3, but not on macOS 10.14.4 with same Qt version. I did not get this error on Windows 10 with Qt 5.5.1.
I tried all the ideas above so this seems to be a bug in Qt 5.12.3 for Windows. Have you found any solution?
Do you use object_parallel_to_source ?
Qt has to stay free or it will die.
-
Do you use object_parallel_to_source ?
-
@Cosmin124 It will be hard to help you without the actual project. At least all project files are needed.
If you want to investigate yourself, check the compile output. sometimes builds fail just because of timing, i.e. dependency is build parallel or after the project that uses the dependency.
Regards
-
Unfortunately I wasn't able to fix it @Cosmin124
-
Are other files from the same directory being included from this dir?
$$PWD/../../../GBusArtifact/Debug/interface/include/routercontroller/routercontroller_fw \Have you tried doing an explicit include:
HEADERS += <absolute path> or HEADERS += <relative path>Are there symbolic links in the path that could be screwing stuff up?
-
this might help:
add the following to .pro fileQMAKE_PROJECT_DEPTH = 0this will make all Makefile includes to absolute paths
-
this might help:
add the following to .pro fileQMAKE_PROJECT_DEPTH = 0this will make all Makefile includes to absolute paths
@saurabhjadhav1911 Add QMAKE_PROJECT_DEPTH = 0 to .pro file works for me, thanks very much.
-
@saurabhjadhav1911 Add QMAKE_PROJECT_DEPTH = 0 to .pro file works for me, thanks very much.
@leon_t
It worked for me, thank you!
Bill -
@saurabhjadhav1911 Add QMAKE_PROJECT_DEPTH = 0 to .pro file works for me, thanks very much.
@leon_t said in Dependent (that clearly exists) does not exist error when building Qt Creator project:
@saurabhjadhav1911 Add QMAKE_PROJECT_DEPTH = 0 to .pro file works for me, thanks very much.
Worked.
-
this might help:
add the following to .pro fileQMAKE_PROJECT_DEPTH = 0this will make all Makefile includes to absolute paths
@saurabhjadhav1911 thanks~
-
@saurabhjadhav1911 Add QMAKE_PROJECT_DEPTH = 0 to .pro file works for me, thanks very much.
@leon_t Amazing! It works! Why?
-
this might help:
add the following to .pro fileQMAKE_PROJECT_DEPTH = 0this will make all Makefile includes to absolute paths
@saurabhjadhav1911 It works for me!!! Thanks a lot
