Comment 10 for bug 1873406

I agree that "Further discussion" as Debian puts it is probably in order here, and we should decide what we want the EpicsHostArch.pl script to be able to do (and who's going to maintain it).

Note that if you don't set EPICS_HOST_ARCH at all and just run 'make' the EPICS build system (in configure/CONFIG) will call the script to set it for the duration of the build. That works reasonably well for the Unix derivatives, but Windows is a very different beast and I don't believe we could hope to detect and support all possible Windows build environments automatically.

Personally (as you probably know) I use Strawberry Perl (as installed by Chocolatey), which comes with copies of GNUmake and gcc. That plus Visual Studio is all I need to be able to build for win32-x86, windows-x64 and windows-x64-mingw so there's no way that the EpicsHostArch.pl script could tell which of those 3 targets I want it to build. I have a series of .bat files that I run beforehand to choose (I don't use the startup .bat files); Janet used to have multiple desktop icons for starting the command shell with different environments. Actually it looks like I stopped bothering with win32-x86 at all when IT upgraded me to Windows 10, does anyone still use 32-bit CPUs to run Windows?