I would like to open a discussion for 72 hours then call a vote. The
topic is "Should we remove Windows native build support?"
There have been several SDKs build for Windows native in the past. One
obstacle for the Windows native build is that it requires a Windows
native port of kconfig-frontends.
That has actually been done a couple of times to support NuttX user SDKs:
* http://uvc.de/posts/linux-kernel-configuration-tool-mconf-under-windows.html
* http://reclonelabs.com/more-kconfig-awesomeness-for-windows/
These work quite nicely. The reclonelabs is the most up-to-date and the
most frequently used. Although the UVC Ingeniere gets credit for being
the first. (I know, there is a Python version too).
The relevance of this these to the current discussion topic is that this
shows the extent to which motivated NuttX users will go to get the pure
Windows native build.
For this small set of users, if NuttX did not build natively on Windows,
they would not use it. So please consider the issues and the PROs and
CONs. Don't base the discussion on what I like to use and how people do
things in the little world I live in. We need to think broadly about
the value of Windows native support before we kiss off potential users.
Greg
