| #
21342d4a |
| 08-Feb-2017 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
| #
8d7523c5 |
| 23-Jan-2017 |
Simon Glass <sjg@chromium.org> |
buildman: Allow showing the list of boards with -n
As well as showing the number of boards, allow showing the actual list of boards that would be built, if -v is provided.
Signed-off-by: Simon Glas
buildman: Allow showing the list of boards with -n
As well as showing the number of boards, allow showing the actual list of boards that would be built, if -v is provided.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
73eed452 |
| 04-Dec-2016 |
Tom Rini <trini@konsulko.com> |
Merge branch 'master' of git://www.denx.de/git/u-boot-dm
|
| #
b464f8e7 |
| 13-Nov-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Squash useless output from -K
When using #define CONFIG_SOME_OPTION, the value it set to '1'. When using defconfig (i.e. CONFIG_SOME_OPTION=y) the value is set to 'y'. This results in diff
buildman: Squash useless output from -K
When using #define CONFIG_SOME_OPTION, the value it set to '1'. When using defconfig (i.e. CONFIG_SOME_OPTION=y) the value is set to 'y'. This results in differences showing up with -K. These differences are seldom useful.
Adjust buildman to suppress these differences by default.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
b50113f3 |
| 13-Nov-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Add an option to just create the config
Normally buildman does a full build of a board. This includes creating the u-boot.cfg file which contains all the configuration options. Buildman us
buildman: Add an option to just create the config
Normally buildman does a full build of a board. This includes creating the u-boot.cfg file which contains all the configuration options. Buildman uses this file with the -K option, to show differences in effective configuration for each commit.
Doing a full build of U-Boot just to create the u-boot.cfg file is wasteful. Add a -D option which causes buildman to only create the configuration. This is enough to support use of -K and can be done much more quickly (typically 5-10 times faster).
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
a2ed3f45 |
| 20-Sep-2016 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
| #
785f1548 |
| 26-Jul-2016 |
Simon Glass <sjg@chromium.org> |
patman: Adjust command.Output() to raise an error by default
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
patman: Adjust command.Output() to raise an error by default
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 <sjg@chromium.org>
show more ...
|
| #
7e92e46e |
| 28-Jul-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Drop the toolchain error when downloading toolchains
It doesn't make sense to complain about missing toolchains when the --fetch-arch option is being used. The user is presumably aware tha
buildman: Drop the toolchain error when downloading toolchains
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 <sjg@chromium.org>
show more ...
|
| #
713bea38 |
| 28-Jul-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Improve the toolchain progress/error output
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 messa
buildman: Improve the toolchain progress/error output
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 <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
show more ...
|
| #
08ca213a |
| 24-May-2016 |
Stefano Babic <sbabic@denx.de> |
Merge branch 'master' of git://git.denx.de/u-boot
|
| #
4b6e1fda |
| 17-May-2016 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
| #
f79f1e0c |
| 11-Apr-2016 |
Stephen Warren <swarren@nvidia.com> |
buildman: allow more incremental building
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
buildman: allow more incremental building
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 <swarren@nvidia.com> Reviewed-by: Tom Rini <trini@konsulko.com> Acked-by: Simon Glass <sjg@chromium.org> # v1 Tested-by: Simon Glass <sjg@chromium.org> # v1 Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
88033d73 |
| 14-Mar-2016 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
| #
2bdeade0 |
| 07-Mar-2016 |
Simon Glass <sjg@chromium.org> |
buildman: patman: Fix -H when installed as a symlink
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 fai
buildman: patman: Fix -H when installed as a symlink
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 <sjg@chromium.org> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com>
show more ...
|
| #
b939689c |
| 05-May-2015 |
Albert ARIBAUD <albert.u.boot@aribaud.net> |
Merge branch 'u-boot/master' into 'u-boot-arm/master'
|
| #
b8d7652c |
| 18-Apr-2015 |
Tom Rini <trini@konsulko.com> |
Merge branch 'buildman' of git://git.denx.de/u-boot-x86
|
| #
843312dc |
| 06-Feb-2015 |
Simon Glass <sjg@chromium.org> |
buildman: Allow comparison of build configuration
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 reporte
buildman: Allow comparison of build configuration
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 <sjg@chromium.org>
show more ...
|
| #
d1c3310d |
| 15-Jan-2015 |
Tom Rini <trini@ti.com> |
Merge branch 'buildman' of git://git.denx.de/u-boot-x86
|
| #
d2ce658d |
| 02-Dec-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add an option to write the full build output
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
buildman: Add an option to write the full build output
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 <sjg@chromium.org>
show more ...
|
| #
827e37b5 |
| 02-Dec-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add the option to download toolchains from kernel.org
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 f
buildman: Add the option to download toolchains from kernel.org
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 <marex@denx.de> Suggested-by: Fabio Estevam <festevam@gmail.com> Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
bb1501f2 |
| 02-Dec-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add an option to use the full tool chain path
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 env
buildman: Add an option to use the full tool chain path
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 <sjg@chromium.org> Suggested-by: Steve Rae <srae@broadcom.com>
show more ...
|
| #
5abab20d |
| 02-Dec-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Allow specifying a range of commits to build
Adjust the -b flag to permit a range expression as well as a branch.
Signed-off-by: Simon Glass <sjg@chromium.org> Suggested-by: Daniel Schwie
buildman: Allow specifying a range of commits to build
Adjust the -b flag to permit a range expression as well as a branch.
Signed-off-by: Simon Glass <sjg@chromium.org> Suggested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
show more ...
|
| #
0740127f |
| 02-Dec-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Don't remove entire output directory when testing
When running tests the output directory is often wiped. This is only safe if a branch is being built. The output directory may contain oth
buildman: Don't remove entire output directory when testing
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 <sjg@chromium.org>
show more ...
|
| #
5971ab5c |
| 02-Dec-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add an option to flatten output directory trees
When building current source for a single board, buildman puts the output in <output_dir>/current/current/<board>. Add an option to make it
buildman: Add an option to flatten output directory trees
When building current source for a single board, buildman puts the output in <output_dir>/current/current/<board>. Add an option to make it use <output_dir>/<board> instead. This removes the unnecessary directories in that case, controlled by the --no-subdirs/-N option.
Suggested-by: Tom Rini <trini@ti.com> Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
2a9e2c6a |
| 02-Dec-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Try to guess the upstream commit
Buildman normally obtains the upstream commit by asking git. Provided that the branch was created with 'git checkout -b <branch> <some_upstream>' then this
buildman: Try to guess the upstream commit
Buildman normally obtains the upstream commit by asking git. Provided that the branch was created with 'git checkout -b <branch> <some_upstream>' 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 <sjg@chromium.org> Suggested-by: Wolfgang Denk <wd@denx.de>
show more ...
|