Closed intat closed 5 years ago
Thanks for the report! I reproduced the problem.
I've decided to upgrade the .vcxproj files to VS2017. For users still working with VS2013 toolset, the old project files are kept as "*2013.vcxproj" and can be invoked with solution file msvc/JuliusLib_vs2013_v120.sln
.
The changes has been commited to master branch.
There are 2 solutions founded.
Visual Studio 2017 showed following errors ( sorry about I use Japanese VS).
following is additional infomations. VS2017 updated this vs projects, Windows SDK to 10.0.17763.0, and Platform Tools Set to v141. OS is windows 10 64bit, but I built in Win32.