1) Concepts section - removed "features", added aflags and lflags 2) Use 1-latest instead of 0-latest in Newt Tool Intro 3) Creating first project tutorial: fixed test "libs/os" package to "sys/config" package and fixed paths listed in debugger.
Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/dc593110 Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/dc593110 Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/dc593110 Branch: refs/heads/develop Commit: dc593110b3ba4183d949bd96c8ee8202b3570ba8 Parents: 7dcb0dc Author: cwanda <wa...@happycity.com> Authored: Fri Mar 31 17:14:55 2017 -0700 Committer: cwanda <wa...@happycity.com> Committed: Sat Apr 1 10:25:54 2017 -0700 ---------------------------------------------------------------------- docs/newt/newt_intro.md | 2 +- docs/os/get_started/project_create.md | 11 ++++++----- docs/os/get_started/vocabulary.md | 6 ++---- 3 files changed, 9 insertions(+), 10 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/dc593110/docs/newt/newt_intro.md ---------------------------------------------------------------------- diff --git a/docs/newt/newt_intro.md b/docs/newt/newt_intro.md index 1b0cf6b..52ddfc4 100644 --- a/docs/newt/newt_intro.md +++ b/docs/newt/newt_intro.md @@ -126,7 +126,7 @@ project.repositories: # repository.apache-mynewt-core: type: github - vers: 0-latest + vers: 1-latest user: apache repo: incubator-mynewt-core ``` http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/dc593110/docs/os/get_started/project_create.md ---------------------------------------------------------------------- diff --git a/docs/os/get_started/project_create.md b/docs/os/get_started/project_create.md index 199fbd5..c7575af 100644 --- a/docs/os/get_started/project_create.md +++ b/docs/os/get_started/project_create.md @@ -230,7 +230,7 @@ into your local directory. ### Test the project's packages -You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the `libs/os` package in the `apache-mynewt-core` repo, call newt as shown below. +You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the `sys/config` package in the `apache-mynewt-core` repo, call newt as shown below. ```no-highlight $ newt test @apache-mynewt-core/sys/config @@ -333,9 +333,10 @@ blink. If you are using newt docker, use `newt run` to run the simulated binary. ```no-highlight $ newt run my_blinky_sim -No download script for BSP hw/bsp/native -Debugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf -<snip> +Loading app image into slot 1 + ... +Debugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf + ... Reading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done. (gdb) ``` @@ -343,7 +344,7 @@ Type `r` at the `(gdb)` prompt to run the project. You will see an output indica If you natively install the toolchain, you can either use `newt run` or call the binary directly. Generally, `newt run` is the expected way to call things. -``` +```no-highlight $ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf hal_gpio set pin 1 to 0 ``` http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/dc593110/docs/os/get_started/vocabulary.md ---------------------------------------------------------------------- diff --git a/docs/os/get_started/vocabulary.md b/docs/os/get_started/vocabulary.md index 6401d55..a716aca 100644 --- a/docs/os/get_started/vocabulary.md +++ b/docs/os/get_started/vocabulary.md @@ -103,9 +103,6 @@ Packages have a few features worth noting: they will inherit their functionality (header files, library definitions, etc.) * APIs: Packages can export named APIs, and they can require that certain APIs be present, in order to compile. - * Features: Packages can operate differently depending on what named features are - present in the system. Packages can also export features to the rest of the - Mynewt system. Everything that newt knows about within a project's directory is a package. This makes it very clean and easy to write re-usable components, which can describe their @@ -127,8 +124,9 @@ of your project. Most targets consist of: Targets can also have additional items specified, including: + * ```aflags```: Any additional assembler flags you might want to specify to the build. * ```cflags```: Any additional compiler flags you might want to specify to the build. - * ```features```: Any system level features you want to enable. + * ```lflags```: Any additional linker flags you might want to specify to the build. In order to create and manipulate targets, the *newt* tool offers a set of helper commands, you can find more information about these by issuing:
