I had exactly the same… nevertheless I redid the whole thing from scratch…
From a fresh repository I had to:
move VCMI…/libs/. into VCMI…/libs/x86/.
In VCMILauncher I had to go to .prj and replace all QT paths
In VCAI I had to create a new macro called FUZZYLITE with value …/FuzzyLite/FuzzyLite
ERM project is not compiling -> out of build configuration (I just dont care about it)
Seems that RD has all debug information inside. So I see no need right now to maintain another configuration. I asked only because I did not knew what to use.
So no I will not add it to the pull request.
The wrong path, came from wrong working directory configured for Launcher. It was $(Project) and should have been $(Solution). I do not completely understand how this dependency is used so I keep a local fix only for myself in VCMI_launcher.vcxproj.user
I found some time to finally complete this. It seems that tutorial will help some people: VCMI VS 2015 build tutorial
This tutorial does not contain all information from previous one, but helps to replace outdated information, and adds some more information about VCMI solution itself.
You can use “outdated” tutorial for tortoise git I guess… I did not use tortoise git so i have no experience with that tool, though I heard some bad opinions about that one. Sourcetree is very popular on windows. Anyway, I use Sourcetree only for “overview” and to view changes. I operate on git command line to perform most actions and I am git first timer :P.