Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
2.4.1
-
Visual Studio Professional 2017
-
-
ceaee1632851b7915d321f30263bbb1919551355
Description
For Configurations Debug and Release, sometimes the following error occurs. Let's concentrate on Debug at first:
Create a new Qt Class Library project (static lib). Create a new Qt Console Project which references the other project, navigate to the Console Project folder and delete the file Debug/qtvars_Win32_Debug.props. After that the 1st build fails with a link error:
{{ 1>LINK : warning LNK4001: no object files specified; libraries used}}
{{ 1>LINK : error LNK2001: unresolved external symbol _mainCRTStartup}}
The 2nd and other builds work again, because the file is regenerated but somehow the settings don't make it into the 1st build after regeneration.
Background: Normally you exclude folder Debug completely from your SCM, so effectively the file qtvars_Win32_Debug.props is missing after the checkout. Besides, the file contains absolute paths to Qt installation dir which breaks the build if the file is in SCM and the path on the system doing the checkout is different.
May be related to QTVSADDINBUG-630
Currently this breaks our build server, on which the error happens more frequently, possibly due to SSD performance on my machine > performance on the build server.