u-boot.git/tools/buildman/control.py, branch v2016.09

buildman: Drop the toolchain error when downloading toolchains

2016-08-01T01:37:08+00:00

It doesn't make sense to complain about missing toolchains when the
--fetch-arch option is being used. The user is presumably aware that there
is a toolchain problem and is actively correcting it by running with this
option.

Refactor the code to avoid printing this confusing message.

Signed-off-by: Simon Glass

buildman: Improve the toolchain progress/error output

2016-08-01T01:37:08+00:00

Use colour to make it easier to see what is going on. Also print a message
before downloading a new toolchain. Mention --fetch-arch in the message that
is shown when there are no available toolchains, since this is the quickest
way to resolve the problem.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini

buildman: allow more incremental building

2016-05-17T15:54:43+00:00

One use-case for buildman is to continually run it interactively after
each small step in a large refactoring operation. This gives more
immediate feedback than making a number of commits and then going back and
testing them. For this to work well, buildman needs to be extremely fast.
At present, a couple issues prevent it being as fast as it could be:

1) Each time buildman runs "make %_defconfig", it runs "make mrproper"
first. This throws away all previous build results, requiring a
from-scratch build. Optionally avoiding this would speed up the build, at
the cost of potentially causing or missing some build issues.

2) A build tree is created per thread rather than per board. When a thread
switches between building different boards, this often causes many files
to be rebuilt due to changing config options. Using a separate build tree
for each board would avoid this. This does put more strain on the system's
disk cache, but it is worth it on my system at least.

This commit adds two command-line options to implement the changes
described above; -I ("--incremental") turns of "make mrproper" and -P
("--per-board-out-dir") creats a build directory per board rather than per
thread.

Tested:

    ./tools/buildman/buildman.py tegra
    ./tools/buildman/buildman.py -I -P tegra
    ./tools/buildman/buildman.py -b tegra_dev tegra
    ./tools/buildman/buildman.py -b tegra_dev -I -P tegra

... each once after deleting the buildman result/work directory, and once
"incrementally" after a previous identical invocation.

Signed-off-by: Stephen Warren 
Reviewed-by: Tom Rini 
Acked-by: Simon Glass  # v1
Tested-by: Simon Glass  # v1
Acked-by: Simon Glass

buildman: patman: Fix -H when installed as a symlink

2016-03-14T21:34:50+00:00

It is convenient to install symlinks to buildman and patman in the search
patch, such as /usr/local/bin. But when this is done, the -H option fails to
work because it looks in the directory containing the symlink instead of its
target. Fix this.

Signed-off-by: Simon Glass 
Reviewed-by: Joe Hershberger

buildman: Allow comparison of build configuration

2015-04-18T22:24:25+00:00

It is useful to be able to see CONFIG changes made by commits. Add this
feature to buildman using the -K flag so that all CONFIG changes are
reported.

The CONFIG options exist in a number of files. Each is reported
individually as well as a summary that covers all files. The output
shows three parts: green for additions, red for removals and yellow for
changes.

Signed-off-by: Simon Glass

buildman: Add an option to write the full build output

2015-01-15T05:16:54+00:00

Normally buildman runs with 'make -s' meaning that only errors and warnings
appear in the log file. Add a -V option to run make in verbose mode, and
with V=1, causing a full build log to be created.

Signed-off-by: Simon Glass

buildman: Add the option to download toolchains from kernel.org

2015-01-15T05:16:54+00:00

The site at https://www.kernel.org/pub/tools/crosstool/ is a convenient
repository of toolchains which can be used for U-Boot. Add a feature to
download and install a toolchain for a selected architecture automatically.

It isn't clear how long this site will stay in the current place and
format, but we should be able to rely on bug reports if it changes.

Suggested-by: Marek Vašut 
Suggested-by: Fabio Estevam 
Signed-off-by: Simon Glass

buildman: Add an option to use the full tool chain path

2015-01-15T05:16:53+00:00

In some cases there may be multiple toolchains with the same name in the
path. Provide an option to use the full path in the CROSS_COMPILE
environment variable.

Note: Wolfgang mentioned that this is dangerous since in some cases there
may be other tools on the path that are needed. So this is set up as an
option, not the default. I will need test confirmation (i.e. that this
commit fixes a real problem) before merging it.

Signed-off-by: Simon Glass 
Suggested-by: Steve Rae

buildman: Allow specifying a range of commits to build

2015-01-15T05:16:53+00:00

Adjust the -b flag to permit a range expression as well as a branch.

Signed-off-by: Simon Glass 
Suggested-by: Daniel Schwierzeck 
Tested-by: Daniel Schwierzeck

buildman: Don't remove entire output directory when testing

2015-01-15T05:16:52+00:00

When running tests the output directory is often wiped. This is only safe if
a branch is being built. The output directory may contain other things
besides the buildman test output.

Signed-off-by: Simon Glass