[GitHub] [incubator-nuttx] btashton commented on issue #886: Cygwin sim:nsh failed on apps/builtin

[GitBox <gi...@apache.org>]

btashton commented on issue #886:
URL: https://github.com/apache/incubator-nuttx/issues/886#issuecomment-619670125


   > The Windows builds are getting more quirky all of the time. I opened a couple of other issues for weird behavior too. Basic problem is that the people who are modifying the build system use Linux. Build testing includes only Linux, but has recently been updated to cover macOS, but no Windows platforms.
   > 
   > This is very big exposure because over 60% of the people who download NuttX (and presumably use it) are on Windows platforms. More than both Linux and macOS combined. Yet there is no development or testing on the most common NuttX user platform.
   > 
   > Reference: https://sourceforge.net/projects/nuttx/files/stats/os?dates=2007-02-01%20to%202020-04-01&period=monthly
   
   Yeah I am going to submit a PR to add CI for windows now that I have an environment to test in.  It should actually not be to bad, but will have to wait until after the RC is out for voting.  The native build will take a bit more work to get wired up correctly, but the Cygwin one was really not bad at all.
   
   For reference this is how I setup the environment:
   Minimal Cygwin with these packages added:
   ```
       make              bison             libmpc-devel
       gcc-core          byacc             automake-1.15
       gcc-g++           gperf             libncurses-devel
       flex              gdb               libmpfr-devel
       git               unzip             zlib-devel
   ```
   Then I built the kconfig-frontend like we do for all the other platforms.
   
   I also did a test with an ARM configuration and for that I just grabbed the zip install from here:
   https://developer.arm.com/-/media/Files/downloads/gnu-rm/9-2019q4/gcc-arm-none-eabi-9-2019-q4-major-win32.zip


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org