Item 2 isn't a good option: a broken build system just give the user a
very bad impression that OS self isn't workable or stable. It's better
that we fully support Windows native or remove from the list at all.
What I means the full is that all config must pass the automation
build and run the build system regularly like other host.
It has always been advertised that way. From the top-level README.txt
which is the only authoritative source:
1442 Native Windows Build
1443 --------------------
1444
1445 The beginnings of a Windows native build are in place but
still not often
1446 used as of this writing. The build was functional but
because of lack of
1447 use may find some issues to be resolved with this build
configuration.
(although "The beginnings of" should be removed)
That has always been there, but people don't always read the
documentation. So your point is well taken.
I have, however, never experienced a case where anyone has misunderstood
the DIY nature of the Native build.
Greg
