Details
-
Bug
-
Resolution: Duplicate
-
Not Evaluated
-
None
-
5.9.5
-
None
-
Visual Studio 2015 & 2017. Windows 10 (x64).
Description
MOC seem to fail silently on missing #include headers. This causes sporadic problems with missing macro expansions in our SW that trigger hard-to-understand errors later in the build process.
Reproducer project attached. The reproducer might appear artificial, but it's based on real-life problems where the missing header first appear after the MOC run, but before the C++ compiler run. This causes the build succeed, despite MOC not expanding macros found in the missing header.
Can you please make MOC more strict, so that it fails immediately when headers are not found?
Attachments
Issue Links
- relates to
-
QTBUG-101760 Add an option to print candidate include paths and the chosen path or failure
- Reported