6a221f3d05
Consider the following source tree: foo/narf.cpp bar/narf.c bar/gnampf.cpp The .pro file has SOURCES += foo/narf.cpp bar/gnampf.cpp The file bar/narf.c is not supposed to be built for whatever reason. QMake's nmake Makefile generator generates inference rules of the form {.\foo}.cpp{debug\}.obj:: ... for every source subdirectory and every source file extension. Thus, we have {.\foo}.cpp{debug\}.obj:: {.\bar}.cpp{debug\}.obj:: {.\bar}.c{debug\}.obj:: Depending on the exact execution order of the inference rules (which depends on the names of the files) the latter rule might get picked, and we're erronously compiling bar/narf.c even though it's not referenced in the .pro file. Conclusion: QMake's detection of conflicting source files must consider the base names of source files, and not the exact file names. Fixes: QTBUG-72059 Change-Id: I50c2725ae2a7421053369a10680230f571af00ea Reviewed-by: Oliver Wolff <oliver.wolff@qt.io> Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io> |
||
---|---|---|
.. | ||
mingw_make.cpp | ||
mingw_make.h | ||
msbuild_objectmodel.cpp | ||
msbuild_objectmodel.h | ||
msvc_nmake.cpp | ||
msvc_nmake.h | ||
msvc_objectmodel.cpp | ||
msvc_objectmodel.h | ||
msvc_vcproj.cpp | ||
msvc_vcproj.h | ||
msvc_vcxproj.cpp | ||
msvc_vcxproj.h | ||
registry_p.h | ||
registry.cpp | ||
winmakefile.cpp | ||
winmakefile.h |