Hmm, first you need the libraries tagged for 2.79a (there is no 2.79b tag, so i assume those are the same) from here https://svn.blender.org/svnroot/bf-blender/tags/blender-2.79a-release/lib/win64_vc14/ since the FM bases on the 2.79b release and in the trunk libs for example there is already python 3.6 (instead of python 3.5, what we need).
Then if you use Visual Studio 2017 Community edition, there is a bug in the CMake files of blender. I pushed a fix for it now, could you please git pull the branch (for updating) ? It just fails to detect the MSVC build files properly due to a wrong version query. In build_files/cmake/platform/platform_win32_msvc.cmake at line 137 it reads
if(MSVC_VERSION EQUAL 1910) but it should read
if(MSVC_VERSION GREATER 1909) there.
That should be the whole fix.
Edit: actually it is the fix ONLY if you build it with cmake and VS 2017 instead of using make.bat.
You need to open cmake (the UI) , specify the source path ( where blenders CMakeLists.txt is) and a build directory (should be separate from the source dir) and hit Configure. Then you choose your compiler and hit Generate, after its finished hit Open Project and it should open VS with the solution file.
There you need to build the project “ALL_BUILD” and the project “INSTALL”. Hmm, seems i forgot that i failed with make and vs 2017 too and had to build it the “old” way because of that…
The “lib” dir should be on the same level as the “blender” dir is, basically you create on that same level an empty “build” dir and use it as build directory in CMake.
Edit 2: make also sure you enable “Grouped” and “Advanced” in CMake gui and check in the “WITH” section stuff you want to include as well ! (like Alembic, FFMPEG, Ocean Modifier, OSL, CUDA binaries (you could also use the official cubins instead of compiling them) and more (WITH_VORO should be checked at all)
Edit 3: I also asked Kai to update the graphicall build, so if all fails, it should be updated soon (like tomorrow or so)