Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-06-01 16:59:28 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Way too many typos

Browse Source
This commit is contained in:
Gregory Nutt
2015-06-30 15:18:57 -06:00
parent 0f3fcd9938
commit 464390193e
1 changed files with 29 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/README.txt
+10 -10
View File
@@ -570,9 +570,9 @@ refresh.sh
testbuild.sh testbuild.sh
------------ ------------
This script automates building of a sequence of configuration. The This script automates building of a set of configurations. The intent is
intent is simply to assure that the set of configurations build simply to assure that the set of configurations build correctly. The -h
correctly. The -h option lists the usage: option shows the usage:
$ ./testbuild.sh -h $ ./testbuild.sh -h
@@ -588,26 +588,26 @@ testbuild.sh
Your PATH variable must include the path to both the build tools and the Your PATH variable must include the path to both the build tools and the
kconfig-frontends tools kconfig-frontends tools
These script needs essential two pieces of information. These script needs two pieces of information.
a. A description of the platform that you are testing on. This a. A description of the platform that you are testing on. This
description is provided by the optiona -w, -l, -c, and -n options. description is provided by the optional -w, -l, -c, and -n options.
b. A list of builds to perform. That list is provided by a test list b. A list of configurations to build. That list is provided by a test
file. The final, non-optional parameter <testlist-file> provides list file. The final, non-optional parameter, <testlist-file>,
the path to that file. provides the path to that file.
The test list file is a sequence of build descriptons, one per line. One The test list file is a sequence of build descriptons, one per line. One
build descriptions consists of two comma separated values. For example: build descriptions consists of two comma separated values. For example:
stm32f429i-disco/nsh,CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIL stm32f429i-disco/nsh,CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIL
The first value is the usual configuration description which of then The first value is the usual configuration description of the form
form <board-name>/<configuration-name> and must correspond to a form <board-name>/<configuration-name> and must correspond to a
configuration in the nuttx/configs directory. configuration in the nuttx/configs directory.
The second value is valid name for a toolchain configuration to use The second value is valid name for a toolchain configuration to use
when building the configuration. The set of valid toolchain when building the configuration. The set of valid toolchain
configuration names depnds on the underlying architecture of the configuration names depends on the underlying architecture of the
configured board. configured board.
zipme.sh zipme.sh