tag | aadba84eb3f706763f0ae15902b67a0297f11cdf | |
---|---|---|
tagger | Szymon Janc <szymon.janc@codecoup.pl> | Thu Jul 27 23:43:32 2017 +0200 |
object | e1c8a7f2294d3f2513eca16aebac12eede542596 |
Mynewt 1.1.0
commit | e1c8a7f2294d3f2513eca16aebac12eede542596 | [log] [tgz] |
---|---|---|
author | Szymon Janc <szymon.janc@codecoup.pl> | Thu Jul 27 23:23:11 2017 +0200 |
committer | GitHub <noreply@github.com> | Thu Jul 27 23:23:11 2017 +0200 |
tree | 6fd4c2467186c789f68e89f8178139922cc7c47d | |
parent | 9e50a2a8bd2b7918a218e25de0a0da8d7cc21ae3 [diff] | |
parent | 689b3c97e15d8bf242e38ffbcbe897a33e4b6604 [diff] |
Merge pull request #14 from ccollins476ad/nmgr-mtu-512 Reduce default MTU from 527 to 512.
Newt Manager (newtmgr) is the application tool that enables a user to communicate with and manage remote devices running the Mynewt OS. It uses a connection profile to establish a connection with a device and sends command requests to the device. Thew newtmgr tool is documented at http://mynewt.apache.org/latest/newtmgr/overview/
newtmgr is vendored using the godep tool (https://github.com/tools/godep). Some dependencies are intentially excluded from the vendor directory. The reason these are not vendored is to prevent errors during elicited by go get mynewt.apache.org/newtmgr/...
on linux. These two dependencies contain OS-specific code, something go get
seems to trip over when it is vendored.
To build newtmgr from source, you will need to manually acquire the missing dependencies. OS-specific instructions are below:
apache-mynewt-newtmgr-1.1.0
directory to $GOPATH/src/mynewt.apache.org/newtmgr
cd $GOPATH/src/mynewt.apache.org/newtmgr/newtmgr
go get github.com/currantlabs/ble github.com/mgutz/logxi/v1 golang.org/x/sys/unix
go build
apache-mynewt-newtmgr-1.1.0
directory to $GOPATH/src/mynewt.apache.org/newtmgr
cd $GOPATH/src/mynewt.apache.org/newtmgr/newtmgr
go get github.com/currantlabs/ble github.com/mgutz/logxi/v1 github.com/raff/goble/xpc
go build