Comment 11 for bug 1873406

I would say, in cases where the user runs the compiler setup (vsvarsall or equivalent script) first, EpicsHostArch could look at a few environment variables and figure out the intended setting in most cases.
It would not detect all possible cases on all possible platforms, certainly, but should the inability to reach perfection keep us from improving it?

Since you do run your compiler setup batch beforehand, I am sure EpicsHostArch could perfectly tell which of those targets you want to build in your Strawberry field.

Older free VisualStudio versions (2008, 2010, 2012) that don't offer the 64bit compiler are the main 32bit reasons I can think of. Not sure about legacy/embedded systems - are those running Windows?