06 Nov, 2016
1 commit
-
The README for buildman says that we can use any field in boards.cfg to
decide what to build. However, we were not saving the options field
correctly.Cc: Simon Glass
Signed-off-by: Tom Rini
Acked-by: Simon Glass
09 Oct, 2016
10 commits
-
Now we can use compiler wrapper such as ccache or distcc for buildman.
Signed-off-by: York Sun
CC: Simon Glass
Acked-by: Simon Glass -
Signed-off-by: York Sun
CC: Simon Glass
Fixed commit subject:
Signed-off-by: Simon Glass
Acked-by: Simon Glass -
This is not used, so drop it.
Signed-off-by: Simon Glass
-
When Ctrl-C is pressed, just exited quietly. There is no sense in displaying
a stack trace since buildman will always be in the same place: waiting for
threads to complete building all the jobs on the queue.Signed-off-by: Simon Glass
-
This serves no real purpose, since when we are not active, we exit. Drop it.
Signed-off-by: Simon Glass
-
It is annoying that buildman does not respond cleanly to Ctrl-C or SIGINT,
particularly on machines with lots of CPUS. Unfortunately queue.join()
blocks the main thread and does not allow it to see the signal. Use a
separate thread instead,Signed-off-by: Simon Glass
-
If patman is installed on the machine (e.g. in the standard dist-packages
directory), it will find libraries from there in preference to our local
libraries. Adjust the order of the path to ensure that local libraries are
found first.Signed-off-by: Simon Glass
-
Make it clear when buildman actually starts building. This happens when it
has prepared the threads, working directory and output directories.Signed-off-by: Simon Glass
-
When buildman starts, it prepares its output directory by removing any old
build directories which will not be used this time. This can happen if a
previous build left directories around for commit hashes which are no-longer
part of the branch.This can take quite a while, so print a message to indicate what is going
on.Signed-off-by: Simon Glass
-
On a machine with a lot of CPUs this prints a lot of useless lines of the
form:Cloning repo for thread
Adjust the output so that these all appear on one line, and disappear when
the cloning is complete.Note: This cloning is actually unnecessary and very wasteful on disk space
(about 3.5GB each time). It would be better to create symlinks.Signed-off-by: Simon Glass
19 Sep, 2016
1 commit
-
It is more useful to have this method raise an error when something goes
wrong. Make this the default and adjust the few callers that don't want to
use it this way.Signed-off-by: Simon Glass
01 Aug, 2016
9 commits
-
For those who just want to build a board, it is useful to see a quick hint
right at the start of the documentation. Add a few commands showing how to
download toolchains and build a board.Signed-off-by: Simon Glass
-
The current code for setting up the toolchain config always writes the new
paths to an item called 'toolchain'. This means that it will overwrite any
existing toolchain item with the same name. In practice, this means that:buildman --fetch-arch all
will fetch all toolchains, but only the path of the final one will be added
to the config. This normally works out OK, since most toolchains are the
same version (e.g. gcc 4.9) and will be found on the same path. But it is
not correct and toolchains for archs which don't use the same version will
not function as expected.Adjust the code to use a complete glob of the toolchain path.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini -
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
-
The function comment should say 'buildman'. Fix it.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini -
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 -
When there are no toolchains a warning is printed. But in some cases this is
confusing, such as when the user is fetching new toolchains.Adjust the function to supress the warning in this case.
Signed-off-by: Simon Glass
-
When buildman is run via a symlink, this test fails. Fix it to work the same
way as buildman itself.Signed-off-by: Simon Glass
-
If there is no ~/.buildman file, buildman currently complains and exists. To
make things a little more friendly, create an empty one automatically. This
will not allow things to be built, but --fetch-arch can be used to handle
that.Signed-off-by: Simon Glass
Reviewed-by: Tom Rini -
Tidy up some problems found by a recent review.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
17 May, 2016
1 commit
-
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
18 Mar, 2016
3 commits
-
This option outputs to the log file, not to the terminal. Clarify that in
the help, and add a mention of it in the README.Signed-off-by: Simon Glass
Reported-by: Stephen Warren
Reviewed-by: Stephen Warren -
At present buildman allows you to specify the directory containing the
toolchain, but not the actual toolchain prefix. If there are multiple
toolchains in a single directory, this can be inconvenient.Add a new 'toolchain-prefix' setting to the settings file, which allows
the full prefix (or path to the C compiler) to be specified.Update the documentation to match.
Suggested-by: Stephen Warren
Reviewed-by: Joe Hershberger
Signed-off-by: Simon Glass
Tested-by: Stephen Warren -
At present if you try to use buildman with the branch 'test' it will
complain that it is unsure whether you mean the branch or the directory.
This is a feature of the 'git log' command that buildman uses. Fix it
by resolving the ambiguity.Signed-off-by: Simon Glass
Reviewed-by: Joe Hershberger
15 Mar, 2016
4 commits
-
At present the architecture is deduced from the toolchain filename. Allow it
to be specified by the caller.Signed-off-by: Simon Glass
Reviewed-by: Joe Hershberger <joe.hershberger@ni.com -
At present the priority of a toolchain is calculated from its filename based
on hard-coded rules. Allow it to be specified by the caller. We will use
this in a later patch. Also display the priority and provide a message when
it is overriden by another toolchain of higher priority.Signed-off-by: Simon Glass
Reviewed-by: Joe Hershberger -
Normally we use a single quote for strings unless there is a reason not to
(such as an embedded single quote). Fix a few counter-examples in this file.
Also add a missing function-argument comment.Signed-off-by: Simon Glass
Reviewed-by: Joe Hershberger -
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
25 Feb, 2016
1 commit
-
Since commit 87da2690ab81b5f29f83dc85c55f933e6ef414bc
"openrisc: updating build tools naming convention", openrisc
kernel.org toolchain is out of date and cannot build U-Boot.
Update buildman and moveconfig tools to refer to the new one.Signed-off-by: Bin Meng
11 Dec, 2015
1 commit
-
Add links for toolchains not available on kernel.org.
The sh4 toolchains from kernel.org dose not work for some boards,
so use the sh from Sourcery.Signed-off-by: Thomas Chou
Reviewed-by: Bin Meng
Reviewed-by: Simon Glass
09 Sep, 2015
1 commit
-
At present buildman can compare configurations between commits but the
feature is less useful than it could be. There is no summary by architecture
and changes are not reported on a per-board basis.Correct these deficiencies so that it is possible to see exactly what is
changing for any number of boards.Note that 'buildman -b -C' is recommended for any build where you
will be comparing configuration. Without -C the correct configuration will
not be reported since changes will often not be picked up.Reviewed-by: Joe Hershberger
Signed-off-by: Simon Glass
29 Aug, 2015
1 commit
-
Corresponds to ba71a0e (Fix _parse_block() 'parent' documentation re.
ifs.) from upstream, just adding the SPDX tag.Has performance improvements, code cleanup, Python 3 support, and various
small fixes, including the following:- Unset user values when loading a zero-byte .config. (5e54e2c)
- Ignore indented .config assignments. (f8a7510)
- Do not require $srctree to be set for non-kernel projects. (d56e9c1)
- Report correct locations in the presence of continuation lines.
(0cebc87)
Signed-off-by: Ulf Magnusson
29 Jul, 2015
1 commit
-
The doc wrongly put sandbox in the '--fetch-arch' command. Remove it.
Signed-off-by: Bin Meng
Acked-by: Simon Glass
15 Jul, 2015
1 commit
-
On i.MX platforms the SPL binary is called "SPL" so make sure we keep
that.Cc: Simon Glass
Signed-off-by: Tom Rini
Acked-by: Simon Glass
13 Jun, 2015
1 commit
-
This commit imports some updates of kconfiglib.py from
https://github.com/ulfalizer/Kconfiglib- Warn about and ignore the "allnoconfig_y" Kconfig option
- Statements in choices inherit menu/if deps
- Add Symbol.is_allnoconfig_y()
- Hint that modules are still supported despite warnings.
- Add warning related to get_defconfig_filename().
- Fix typo in docs.
- Allow digits in $-references to symbols.Signed-off-by: Ulf Magnusson
Signed-off-by: Philip Craig
Signed-off-by: Jakub Sitnicki
Signed-off-by: Masahiro Yamada
24 Apr, 2015
1 commit
-
Also read gcc 4.9.0 at kernel.org which also have Microblaze toolchain.
Signed-off-by: Michal Simek
Acked-by: Simon Glass
Tested-by: Simon GlassFixed unit test failure by updating the test:
Signed-off-by: Simon Glass
19 Apr, 2015
3 commits
-
The help text for -V says we will pass V=1 but all it really did was not
pass in -s. Change the logic to pass make V=1 with given to buildman -V or
-s to make otherwise.Cc: Simon Glass
Signed-off-by: Tom Rini
Acked-by: Simon Glass -
When told to keep outputs, be much more liberal in what files we keep.
In addition to adding 'MLO', keep anything that matches u-boot-spl.* (so
that we keep the map file as well) and anything we generate about
'u-boot itself. A large number of bootable formats now match this and
thus it's easier to build many targets and then boot them afterwards
using buildman.Cc: Simon Glass
Signed-off-by: Tom Rini
Acked-by: Simon Glass -
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