Ah yes... Since I restricted the build types to "Release" only for Windows, such a command is now possible without an auxiliary tool (LL uses a custom VSTool.exe to configure the build type, else it defaults to Debug, whatever the type you pass to msbuild)...
However, I do not have VS2017 installed in the directory you quote in the batch file. Also, the Python executable should already be in your PATH (else the windows-prebuild-vs2017.bat script won't work in the first place). Finally, using %CD% instead of an absolute path allows to just double-click on the batch file (when it is placed along windows-prebuild-vs2017.bat) to build the viewer, wherever you place its sources. Oh, and you do not need to pass the CL_MPCount parameter (the cmake files already specify /MP, that VS should adapt automatically to the available cores). Here is a modified script that should work for default VS2017 Community Edition installations:
This said, I do not use ssh to compile the Windows (and Linux) builds, but a VirtualBox VM (that I start only when I need to produce a new official build)... So, it would mean using the Windows terminal/console instead, which is extremely poor (in particular with only a limited scroll back history, not resizable in width, etc...). I definitely prefer the GUI (especially to debug the VS2017 idiosyncrasies that sometimes cause a new release to fail building at my first try).
I'll add the build script to next release however. Thanks for the suggestion !
