sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests 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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
tools/README.txt
View File

@ -570,45 +570,45 @@ refresh.sh
testbuild.sh
------------
This script automates building of a sequence of configuration. The
intent is simply to assure that the set of configurations build
correctly. The -h option lists the usage:
This script automates building of a set of configurations. The intent is
simply to assure that the set of configurations build correctly. The -h
option shows the usage:
$ ./testbuild.sh -h
$ ./testbuild.sh -h
USAGE: ./testbuild.sh [-w|l] [-c|n] <testlist-file>
USAGE: ./testbuild.sh -h
USAGE: ./testbuild.sh [-w|l] [-c|n] <testlist-file>
USAGE: ./testbuild.sh -h
where
-w|l selects Windows (w) or Linux (l). Default: Linux
-c|n selects Windows native (n) or Cygwin (c). Default Cygwin
-h will show this help test and terminate
<testlist-file> selects the list of configurations to test. No default
where
-w|l selects Windows (w) or Linux (l). Default: Linux
-c|n selects Windows native (n) or Cygwin (c). Default Cygwin
-h will show this help test and terminate
<testlist-file> selects the list of configurations to test. No default
Your PATH variable must include the path to both the build tools and the
kconfig-frontends tools
Your PATH variable must include the path to both the build tools and the
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
description is provided by the optiona -w, -l, -c, and -n options.
b. A list of builds to perform. That list is provided by a test list
file. The final, non-optional parameter <testlist-file> provides
the path to that file.
a. A description of the platform that you are testing on. This
description is provided by the optional -w, -l, -c, and -n options.
b. A list of configurations to build. That list is provided by a test
list file. The final, non-optional parameter, <testlist-file>,
provides the path to that file.
The test list file is a sequence of build descriptons, one per line. One
build descriptions consists of two comma separated values. For example:
The test list file is a sequence of build descriptons, one per line. One
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
form <board-name>/<configuration-name> and must correspond to a
configuration in the nuttx/configs directory.
The first value is the usual configuration description of the form
form <board-name>/<configuration-name> and must correspond to a
configuration in the nuttx/configs directory.
The second value is valid name for a toolchain configuration to use
when building the configuration. The set of valid toolchain
configuration names depnds on the underlying architecture of the
configured board.
The second value is valid name for a toolchain configuration to use
when building the configuration. The set of valid toolchain
configuration names depends on the underlying architecture of the
configured board.
zipme.sh
--------