Windows 10 msvc_build.bat with debug parameter fails
at the command prompt: msvc_build.bat debug
It's failing because it is expecting a VS2010 toolset. I have tried various things inside VS2017 (there is no "Retarget Solution" option), and I have examined the batch file itself: no success. I don't want to install the VS2010 build tools. Is this a problem with the makefiles? I am going to revert to the RelWithDebugInfo configuration for now, but I would really like to build a full debug build. RelWithDebugInfo prevents me from putting breakpoints on some lines, among other optimizations that leave me half blind. It also might be the cause of some other irregular behavior on the part of the VS2017 debugger, at least that's my hope.
The complete error message (which occurs for every sub-project):
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargetsMicrosoft.Cpp.Platform.targets(65,5): error MSB8020:
The build tools for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please install Visual Studio 2010 build tools.
Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
[Z:\MuseScore\msvc.build_x64\ZERO_CHECK.vcxproj]
Comments
I realize that VS2017 is now or will be soon the official platform for building MuseScore. But my experience in the past few weeks has not been particularly positive, especially when debugging dialog boxes and Qt widgets & signals. Maybe there are more uses for Qt Creator than just editing the dialog boxes and inspector panels in a GUI.
Debugging in Qt has its own limitations, but I've been seeing some very irregular behaviors in VS2017. It is only now occurring to me that these are happening when I'm debugging inside Qt dialogs, and that maybe Qt Creator is better suited for that than VS2017. Signals are firing twice when breakpoints are present, for example - that's a consistent bummer. But there are other more sporadic problems with variable assignments and the ability to see locally declared variable values in the debugger. I was hoping a full debug build in VS2017 might set things straight, but I have to reconfigure my Qt Creator back to normal and try debugging there now too.
Just bumping this up the list in the forum to see if I can get answer here. Thanks.
It's the same here for
msvc_build.bat debug. Missing Platform Toolset = 'v100'.Regarding the missing debug info in RelWithDebugInfo, you can set the property C++/Optimization of the libmscore and mscore projects to Deactivated (/0d). Then all variables are available in the debugger.
In reply to It's the same here for msvc… by tobik
Thanks for the confirmation and thanks very much for the workaround. I'll be giving that a try.
In reply to Thanks for the confirmation… by sideways
Delete msvc.install_x64 and msvc.build_x64. This worked for me.