The Windows Cygwin build is a lot slower but it works. (See my video). My vote goes to keeping Windows. It keeps Nuttx followers and Windows is, as stated before, really making effort to support the IoT concept. And its also getting better in Open Source projects. Also their Cloud (Edge) solutions are beating IBM..... in IDE and tooling they also make new efforts...
Post a Windows related video and you will get 10x followers easy.... also many Engineering Companies and Engineers wok primarily in a Windows host. So the have to setup Virtual environments to establish a development environment. Also Nuttx had a “build and run everywhere” feeling and POSIX is also Windows... Why is Nuttx reviewing its core principles? What does Nuttx keep distinguished from its competitors.... loosing the BSD license already had impact.... Is the numbers of participants going up again? Does this effort already show benefits? First keep it like it is and Windows users did their thing and had questions... because it was still an option. First things first right? Focus on whats really important and get contributers back and get trust back in the solid platform (in perspective because testing could be a lot better in drivers etc)..... Arduino is getting into the STM stack and if an RTOS is compliant with that platform then people will go for that option..... why? Because noobs can “make things”..... My 2 cents and just saying... Verstuurd vanaf mijn iPhone > Op 16 jan. 2020 om 14:48 heeft Gregory Nutt <spudan...@gmail.com> het > volgende geschreven: > > >> What I means the full is that all config must pass the automation >> build and run the build system regularly like other host. > > Yes, the problem is a circular one. Why is the native build always out of > date? Because it is not tested. Why don't we test it? Because it is out of > date. > > There are only two ways to break that circular dependency: Remove it or make > it work. There is less inertia to removing it but I don't think that is a > good decision. Is it not motivated only by making the job easier? > > I have not tried a native build in some time. I will try that later today. > There is only one native build configuration in the repository: > stm32f4discovery:winbuild. Let me experiment a little to see where things > are. > >