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

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

buildman: Add an option to flatten output directory trees

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

When building current source for a single board, buildman puts the output
in /current/current/. Add an option to make it use
/ instead. This removes the unnecessary directories
in that case, controlled by the --no-subdirs/-N option.

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

buildman: Try to guess the upstream commit

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

Buildman normally obtains the upstream commit by asking git. Provided that
the branch was created with 'git checkout -b  ' then
this normally works.

When there is no upstream, we can try to guess one, by looking up through
the commits until we find a branch. Add a function to try this and print
a warning if buildman ends up relying on it.

Also update the documentation to match.

Signed-off-by: Simon Glass 
Suggested-by: Wolfgang Denk

buildman: Put build in 'current', not 'current/current'

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

Buildman currently puts current-source builds in a current/current
subdirectory, but there is no need for the extra depth.

Suggested-by: Albert Aribaud 
Signed-off-by: Simon Glass

patman: Use the full commit hash for 'git checkout'

2014-11-03T21:12:39+00:00

Even with the initial 8 characeters of the hash we will sometimes get a
collision. Use the full hash.

Signed-off-by: Simon Glass