Rewrite compile.bat and Update GA workflow to build binaries on Windows: Use Git Version, Use MSBuild, and Allow custom Boost and MSBuild paths

[rwxayheee]

This is a renovation of current build approach on Windows. To address Issue #390.

Expect to add an installation note in doc for people who want to build binaries on Windows.

[rwxayheee]

Previously, the versions of the project, and the versions and locations of boost library were all hard-coded in the vcxproj files. This PR updates the build approach for Windows executables (vina.exe and vina_split.exe):

• Replace the builder, Common7\IDE\devenv.com, by MSBuild for flexible installation and better control

This is also available

• Getting Git Version in a similar manner to the build process on Linux/Mac

The artifact has version information similar to this:

AutoDock Vina v1.2.6-56-gc28e340

• Customizable Boost location, and hereby more flexible with Boost version
  The steps in the GA workflow showcase a usage of the new compile.dat, in PowerShell:

.\compile.bat Release x64 "C:\local\boost_1_83_0\lib64-msvc-14.2" "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\MSBuild.exe" "$env:GIT_VERSION"

Here, 5 variables are passed in order to specify:

• Configuration (see options in vcxproj)
• Platform (see options in vcxproj)
• Path of Boost Library. The Boost Include path (for header files) is interpreted based on the Boost Library Path (within vcxproj)
• Path of MSBuild Executable. In theory, a full installation of Visual Studio is not required.
• Git Version. This can be overriden by anything when people try to compile Vina by themselves. The default is Git Version.

An installation guide can be added to documentation, when this is in release. Building on WIndows with this approach currently requires:

• Boost library
• MSBuild
• Git (optional, for versioning)

[joanimato]

I can't test this personally, but since the tests pass I'll assume everything works ok.

[joanimato]

Let's leave this as it is, reporting both the os and arch.

[rwxayheee]

We have specifc name including arch for each step. The generic name here might not apply. Here because we didn't define arch type for windows (not sure why though..) this might fail. I can try though!

[rwxayheee]

You are right that the name still shows up in the log file. The individual job name follows the name of each step. I will make the correction. I can improve the names

[rwxayheee]

I can't test this personally, but since the tests pass I'll assume everything works ok.

Thanks! I can test on two more Windows computers with slightly different configurations.

[rwxayheee]

Tested on two more systems to make sure compile.bat can compile on older systems without powershell.

Made a small change in 3ba69f1 to allow compilation with different versions of msvc. Previously, msvc-v142 is hardcoded in vcxproj and it works for Visual Studio 2019 (v16.x). As of today, the official website is featuring Visual Studio 2022 (v17.x) and build tools, which need msvc-143.

This is ready :D can be merged any time. thanks!!