Installing Newt on Windows
You can develop and build Mynewt OS applications for your target boards on the Windows platform. This guide shows you how to install the latest release version of newt from binary or from source. The tool is written in Go (golang).
In Windows, we use MinGW as the development environment to build and run Mynewt OS applications for target boards. MinGW runs the bash shell and provides a Unix-like environment. This provides a uniform way to build Mynewt OS applications. The Mynewt documentation and tutorials use Unix commands and you can use the same Unix commands on MinGW to follow the tutorials. The documentation will note any commands or behaviors that are specific to Windows.
This guide shows you how to perform the following:
- Install MSYS2/MinGW.
- Install Git.
- Install latest release of newt (1.2.0) from binary.
- Install latest release of newt from source.
See Installing Previous Releases of Newt to install an earlier version of newt. You still need to set up your MinGW development environment.
Note: If you would like to contribute to the newt tool, see Setting Up Go Environment to Contribute to Newt and Newtmgr Tools.
MSYS2/MinGW provides a bash shell and tools to build applications that run on Windows. It includes three subsystems:
- MSYS2 toolchain to build POSIX applications that run on Windows.
- MinGW32 toolchains to build 32 bit native Windows applications.
- MinGW64 toolchains to build 64 bit native Windows applications.
The subsystems run the bash shell and provide a Unix-like environment. You can also run Windows applications from the shell. We will use the MinGW subsystem.
Note: You can skip this installation step if you already have MinGW installed (from an earlier MSYS2/MinGW or Git Bash installation), but you must list the bin path for your installation in your Windows Path. For example: if you installed MSYS2/MinGW in the C:\msys64 directory, add C:\msys64\usr\bin to your Windows Path. If you are using Windows 10 WSL, ensure that you use the C:\msys64\usr\bin\bash.exe and not the Windows 10 WSL bash.
To install and setup MSYS2 and MinGW:
- Download and run the MSYS2 installer. Select the 64 bit version if you are running on a 64 bit platform. Follow the prompts and check the
Run MSYS2 nowcheckbox on the
In the MSYS2 terminal, run the
pacman -Syuucommand. If you get a message to run the update again, close the terminal and run the
pacman -Syuucommand in a new terminal.
To start a new MSYS2 terminal, select the "MSYS2 MSYS" application from the Windows start menu.
Add a new user variable named MSYS2_PATH_TYPE and set the value to inherit in your Windows environment. This enables the MSYS2 and MinGW bash to inherit your Windows user Path values.
To add the variable, select properties for your computer > Advanced system settings > Environment Variables > New
Add the MinGW bin path to your Windows Path. For example: if you install MSYS2/MinGW in the C:\msys64 directory, add C:\msys64\usr\bin to your Windows Path.
Note: If you are using Windows 10 WSL, ensure that you use the C:\msys64\usr\bin\bash.exe and not the Windows 10 WSL bash.
pacman -Su vimcommand to install the vim editor.
Note:You can also use a Windows editor. You can access your files from the C:\<msys-install-folder>\home\<username> folder, where msys-install-folder is the folder you installed MSYS2 in. For example, if you installed MSYS2 in the msys64 folder, your files are stored in C:\msys64\home\<username>
You will need to start a MinGW terminal to run the commands specified in the Mynewt documentation and tutorials. To start a MinGW terminal, select the "MSYS2 Mingw" application from the start Menu (you can use either MinGW32 or MinGW64). In Windows, we use the MinGW subsystem to build Mynewt tools and applications.
Installing Git for Windows
Download and install Git for Windows if it is not already installed.
Installing the Latest Release of the Newt Tool from Binary
You can install the latest release of newt from binary. It has been tested on Windows 10 64 bit platform.
1. Start a MinGW terminal.
2. Download the newt binary tar file:
$ wget -P /tmp https://raw.githubusercontent.com/runtimeco/binary-releases/master/mynewt-newt-tools_1.2.0/newt_1_2_0_windows_amd64.tar.gz
3. Extract the file:
If you previously built newt from the master branch, you can extract the file into your $GOPATH/bin directory. Note: This overwrites the current newt.exe in the directory and assumes that you are using $GOPATH/bin for your Go applications.
tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C $GOPATH/bin
If you are installing newt for the first time and do not have a Go workspace setup, you can extract into /usr/bin directory:
tar -xzf /tmp/newt_1_2_0_windows_amd64.tar.gz -C /usr/bin
4. Verify the installed version of newt. See Checking the Installed Version.
Installing the Latest Release of Newt From Source
If you have an older version of Windows or a 32 bit platform, you can build and install the latest release version of newt from source.
1. If you do not have Go installed, download and install the latest version of Go. Newt requires Go version 1.7.6 or higher.
2. Start a MinGw terminal.
3. Download and unpack the newt source:
$ wget -P /tmp https://github.com/apache/mynewt-newt/archive/mynewt_1_2_0_tag.tar.gz $ tar -xzf /tmp/mynewt_1_2_0_tag.tar.gz
4. Run the build.sh to build the newt tool.
$ cd mynewt-newt-mynewt_1_2_0_tag $ ./build.sh $ rm /tmp/mynewt_1_2_0_tag.tar.gz
5. You should see the
newt/newt.exe executable. Move the executable to a bin directory in your PATH:
If you previously built newt from the master branch, you can move the executable to the $GOPATH/bin directory.
$ mv newt/newt.exe $GOPATH/bin
If you are installing newt for the first time and do not have a Go workspace set up, you can move the executable to /usr/bin or a directory in your PATH:
$ mv newt/newt.exe /usr/bin
1. Check the version of newt:
$ newt version Apache Newt version: 1.2.0
2. Get information about newt:
Newt allows you to create your own embedded application based on the Mynewt operating system. Newt provides both build and package management in a single tool, which allows you to compose an embedded application, and set of projects, and then build the necessary artifacts from those projects. For more information on the Mynewt operating system, please visit https://mynewt.apache.org/. Please use the newt help command, and specify the name of the command you want help for, for help on how to use a specific command Usage: newt [flags] newt [command] Examples: newt newt help [<command-name>] For help on <command-name>. If not specified, print this message. Available Commands: build Build one or more targets clean Delete build artifacts for one or more targets create-image Add image header to target binary debug Open debugger session to target info Show project info install Install project dependencies load Load built target to board mfg Manufacturing flash image commands new Create a new project pkg Create and manage packages in the current workspace resign-image Re-sign an image. run build/create-image/download/debug <target> size Size of target components sync Synchronize project dependencies target Commands to create, delete, configure, and query targets test Executes unit tests for one or more packages upgrade Upgrade project dependencies vals Display valid values for the specified element type(s) version Display the Newt version number Flags: -h, --help Help for newt commands -j, --jobs int Number of concurrent build jobs (default 8) -l, --loglevel string Log level (default "WARN") -o, --outfile string Filename to tee output to -q, --quiet Be quiet; only display error output -s, --silent Be silent; don't output anything -v, --verbose Enable verbose output when executing commands Use "newt [command] --help" for more information about a command.