incubator-nuttx | Apache NuttX is a mature , real-time embedded operating

Installation instructions abound on the Internet complete with screen shots. I will attempt to duplicate those instructions in full here. Here are the simplified installation steps:. Now that you completed the installation and setup, you can open the Bash tool from the Start menu like you would with any other app.
Open Settings.
Click on Update & security.
Click on For Developers.
Under Use developer features, select the Developer mode option to setup the environment to install Bash.
A message box should pop up. Click Yes to turn on developer mode.
After the necessary components install, you'll need to restart your computer. Once your computer reboots:
Open Control Panel.
Click on Programs.
Click on Turn Windows features on or off.
A list of features will pop up, check the Windows Subsystem for Linux (beta) option.
Click OK.
Once the components installed on your computer, click the Restart now button to complete the task. After your computer restarts, you will notice that Bash will not appear in the Recently added list of apps, this is because Bash isn't actually installed yet. Now that you have setup the necessary components, use the following steps to complete the installation of Bash:
Open Start, do a search for bash.exe, and press Enter.
On the command prompt, type y and press Enter to download and install Bash from the Windows Store. This will take awhile.
Then you'll need to create a default UNIX user account. This account doesn't have to be the same as your Windows account. Enter the username in the required field and press Enter (you can't use the username admin).
Close the bash.exe command prompt.
Use sudo apt-get install <package name>. As examples, this is how you would get GIT:.
There are two ways to get NuttX: You may download released, stable tarballs from either the project website. Or you may get NuttX by cloning the GIT repositories. Let's consider the released tarballs first:.
Download and unpack the NuttX tarball. If you are reading this, then you have probably already done that. After unpacking, you will end up with a directory called nuttx-version (where version is the NuttX version number). You might want to rename that directory nuttx to match the various instructions in the documentation and some scripts in the source tree.
Download location: https://nuttx.apache.org/download/
Legacy download locations: https://bitbucket.org/nuttx/nuttx/downloads https://sourceforge.net/projects/nuttx/files/nuttx/
The nuttx build directory should reside in a path that contains no spaces in any higher level directory name. For example, under Cygwin, your home directory might be formed from your first and last names like: /home/First Last. That will cause strange errors when the make system tries to build. [Actually, that problem is probably not too difficult to fix. Some Makefiles probably just need some paths within double quotes]. I work around spaces in the home directory name, by creating a new directory that does not contain any spaces, such as /home/nuttx. Then I install NuttX in /home/nuttx and always build from /home/nuttx/nuttx-code.
Below is a summary of the build targets available in the top-level NuttX Makefile:. Application housekeeping targets. The APPDIR variable refers to the user application directory. A sample apps/ directory is included with NuttX, however, this is not treated as part of NuttX and may be replaced with a different application directory. For the most part, the application directory is treated like any other build directory in the Makefile script. However, as a convenience, the following targets are included to support housekeeping functions in the user application directory from the NuttX build directory. The following targets are used internally by the make logic but can be invoked from the command under certain conditions if necessary.
all The default target builds the NuttX executable in the selected output formats.
clean Removes derived object files, archives, executables, and temporary files, but retains the configuration and context files and directories.
distclean Does 'clean' then also removes all configuration and context files. This essentially restores the directory structure to its original, unconfigured stated.
apps_clean Perform the clean operation only in the user application directory
apps_distclean Perform the distclean operation only in the user application directory. The apps/.config file is preserved so that this is not a "full" distclean but more of a configuration "reset" for the application directory.
export The export target will package the NuttX libraries and header files into an exportable package. Caveats: (1) These needs some extension for the KERNEL build. (2) The logic in tools/mkexport.sh only supports GCC and, for example, explicitly assumes that the archiver is 'ar'
flash (or download : DEPRECATED) This is a helper target that will rebuild NuttX and flash it to the target system in one step. The operation of this target depends completely upon implementation of the FLASH command in the user Make.defs file. It will generate an error if the FLASH command is not defined.
depend Create build dependencies. (NOTE: There is currently no support for build dependencies under Cygwin using Windows-native toolchains.)
context The context target is invoked on each target build to assure that NuttX is properly configured. The basic configuration steps include creation of the the config.h and version.h header files in the include/nuttx directory and the establishment of symbolic links to configured directories.
clean_context This is part of the distclean target. It removes all of the header files and symbolic links created by the context target.
Of course, the value any make variable an be overridden from the make command line. However, there is one particular variable assignment option that may be useful to you:.
V=1 This is the build "verbosity flag." If you specify V=1 on the make command line, you will see the exact commands used in the build. This can be very useful when adding new boards or tracking down compile time errors and warnings (Contributed by Richard Cochran).
The beginnings of a Windows native build are in place but still not often used as of this writing. The build was functional but because of lack of use may find some issues to be resolved with this build configuration.
Uses all Windows style paths
Uses primarily Windows batch commands from cmd.exe, with
A few extensions from GNUWin32
It has not been verified on all targets and tools, and
it still lacks some of the creature-comforts of the more mature environments.