On Fri, Nov 20, 2020 at 10:01 PM, Jeffrey Melton wrote in part:
BTW - A few weeks ago I'd sent you an email regarding your Windows build instructions for SDL Hyperion and have yet to get a response. The Property Sheet modifications as documented in your instructions cannot be done for a clean install of Visual Studio 2019, as those property sheets don't exist? Are there alternate instructions for ensuring that the 'win32.mak' is included for VS2019?
Thanks!? ? BTW - I do like your HercGUI and HercPRT tools and will be in touch with you about purchasing them.?
Jeffrey and Fish,
(in what follows, please excuse my ignorance of how to format messages in Groups.IO)
VS2019 seems to change to be updated quite often and seems to change its mind
about things a lot.? It has become a very aggravating moving target.
Today (22 Oct 2020) I created a fresh Windows 10 20H2 under VMware, and installed VS2019 16.8.2.
I selected workload "Desktop Development with C++", and under Individual Components, selected
"C++ Windows XP Support for VS 2017 (v141) tools (Deprecated)"
After installation, I used Start / Settings / System / About / Advanced System Settings / Environment Variables
and created:
?? INCLUDE=C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include
I then rebooted.
Open from Start menu, VS2019 x64 Native Tools Command Prompt.
In that command prompt window, I changed to SDL-Hercules git clone directory, and ran:
?? MAKEFILE.BAT RETAIL MAKEFILE.MSVC 8 -title "WRL Test Build" -a
And it worked.? Hercules got built, and what it built works.
---
To get it to build inside Visual Studio itself, there was more tweaking needed.
In? C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160
is a file called Microsoft.Cpp.Common.props.
In that file I found this line:
?? <UserRootDir Condition="'$(UserRootDir)' == '' ">$(LocalAppData)\Microsoft\MSBuild\v4.0</UserRootDir>
On this test system that expands to:
?? C:\Users\bill\AppData\Local\Microsoft\MSBuild\v4.0
Which didn't exist.? So I created the directory.? It also required Show Hidden Files option to work in there.
(Note, that is the directory that VS2017 used, and that does not match MSFT published info related to
property sheets in VS2019 that I found some months ago)
Then I copied my old Microsoft.Cpp.x64.user.props (from another working system with VS2017).
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
? <PropertyGroup>
??? <IncludePath>$(VC_IncludePath);$(WindowsSDK_IncludePath);$(INCLUDE);</IncludePath>
? </PropertyGroup>
</Project>
Building under VS2019 GUI then worked .
I did not attempt a Debug build or to debug anything.
Is it time to start drinking yet?? <sigh>
Bill
