Mirrors/u-boot
2
0
Fork 0
mirror of https://github.com/AsahiLinux/u-boot synced 2024-11-10 23:24:38 +00:00
Code Issues Projects Releases Packages Wiki Activity

buildman: Fix some typos in README

Browse source 
Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Dirk Behme 2014-12-23 07:41:26 +01:00 committed by Tom Rini
parent 3ef46a998a
commit 3e1ded1fff
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
tools/buildman/README
View file

@ -42,7 +42,7 @@ Theory of Operation
Buildman is a builder. It is not make, although it runs make. It does not Buildman is a builder. It is not make, although it runs make. It does not
produce any useful output on the terminal while building, except for produce any useful output on the terminal while building, except for
progress information (except with -v, see below). All the output (errors, progress information (except with -v, see below). All the output (errors,
warnings and binaries if you are ask for them) is stored in output warnings and binaries if you ask for them) is stored in output
directories, which you can look at while the build is progressing, or when directories, which you can look at while the build is progressing, or when
it is finished. it is finished.
@ -121,7 +121,7 @@ You can also use -x to specifically exclude some boards. For example:
means to build all arm boards except nvidia, freescale and anything ending means to build all arm boards except nvidia, freescale and anything ending
with 'ball'. with 'ball'.
It is convenient to use the -n option to see whaat will be built based on It is convenient to use the -n option to see what will be built based on
the subset given. the subset given.
Buildman does not store intermediate object files. It optionally copies Buildman does not store intermediate object files. It optionally copies
@ -371,7 +371,7 @@ in an hour and 15 minutes. Use this time to buy a faster computer.
To find out how the build went, ask for a summary with -s. You can do this To find out how the build went, ask for a summary with -s. You can do this
either before the build completes (presumably in another terminal) or or either before the build completes (presumably in another terminal) or
afterwards. Let's work through an example of how this is used: afterwards. Let's work through an example of how this is used:
$ ./tools/buildman/buildman -b lcd9b -s $ ./tools/buildman/buildman -b lcd9b -s
@ -439,7 +439,7 @@ again.
At commit 16, the error moves - you can see that the old error at line 120 At commit 16, the error moves - you can see that the old error at line 120
is fixed, but there is a new one at line 126. This is probably only because is fixed, but there is a new one at line 126. This is probably only because
we added some code and moved the broken line father down the file. we added some code and moved the broken line further down the file.
If many boards have the same error, then -e will display the error only If many boards have the same error, then -e will display the error only
once. This makes the output as concise as possible. To see which boards have once. This makes the output as concise as possible. To see which boards have
@ -647,8 +647,8 @@ This shows that commit 19 has increased text size for arm (although only one
board was built) and by 96 bytes for powerpc. This increase was offset in both board was built) and by 96 bytes for powerpc. This increase was offset in both
cases by reductions in rodata and data/bss. cases by reductions in rodata and data/bss.
Shown below the summary lines is the sizes for each board. Below each board Shown below the summary lines are the sizes for each board. Below each board
is the sizes for each function. This information starts with: are the sizes for each function. This information starts with:
add - number of functions added / removed add - number of functions added / removed
grow - number of functions which grew / shrunk grow - number of functions which grew / shrunk
@ -817,7 +817,7 @@ TODO
This has mostly be written in my spare time as a response to my difficulties This has mostly be written in my spare time as a response to my difficulties
in testing large series of patches. Apart from tidying up there is quite a in testing large series of patches. Apart from tidying up there is quite a
bit of scope for improvement. Things like better error diffs and easier bit of scope for improvement. Things like better error diffs and easier
access to log files. Also it would be nice it buildman could 'hunt' for access to log files. Also it would be nice if buildman could 'hunt' for
problems, perhaps by building a few boards for each arch, or checking problems, perhaps by building a few boards for each arch, or checking
commits for changed files and building only boards which use those files. commits for changed files and building only boards which use those files.