Hi Masahiro, On 1 August 2014 02:10, Masahiro Yamada <yamad...@jp.panasonic.com> wrote: > Hi. > > > On Mon, 28 Jul 2014 23:53:29 -0600 > Simon Glass <s...@chromium.org> wrote: > >> For those used to MAKEALL, buildman seems strange. Add some notes to ease >> the transition. >> >> Signed-off-by: Simon Glass <s...@chromium.org> >> --- >> >> Changes in v2: >> - Minor changes to the text >> >> tools/buildman/README | 92 >> +++++++++++++++++++++++++++++++++++++++++++++++++++ >> 1 file changed, 92 insertions(+) >> >> diff --git a/tools/buildman/README b/tools/buildman/README >> index a5d181c..1c919af 100644 >> --- a/tools/buildman/README >> +++ b/tools/buildman/README >> @@ -3,6 +3,8 @@ >> # SPDX-License-Identifier: GPL-2.0+ >> # >> >> +(Please read 'How to change from MAKEALL' if you are used to that tool) >> + >> What is this? >> ============= >> >> @@ -663,6 +665,96 @@ Other options >> Buildman has various other command line options. Try --help to see them. >> >> >> +How to change from MAKEALL >> +========================== >> + >> +Buildman includes most of the features of MAKEALL and is generally faster >> +and easier to use. In particular it builds entire branches: if a particular >> +commit introduces an error in a particular board, buildman can easily show >> +you this, even if a later commit fixes that error. >> + >> +The reasons to deprecate MAKEALL are: >> +- We don't want to maintain two build systems >> +- Buildman is typically faster >> +- Buildman has a lot more features >> + >> +But still, many people will be sad to lose MAKEALL. If you are used to >> +MAKEALL, here are a few pointers. >> +First you need to set up your tool chains - see the 'Setting up' section >> +for details. Once you have your required toolchain(s) detected then you are >> +ready to go. >> + >> +Buildman works on entire branches, so the normal use is: >> + >> + ./tools/buildman/buildman -b <branch_name> <list of things to build> >> + >> +followed by (afterwards, or perhaps concurrently in another terminal): >> + >> + ./tools/buildman/buildman -b <branch_name> -s <list of things to build> > > > The biggest difference I see between buildman and MAKEALL is that > buildman tests commits in git-log, > whereas MAKEALL tests the current source tree. > > It means buildman does not work for tarball users. > Maybe we can excuse because I guess most develpers are working on a git-repo. > > But I find MAKEALL is much eaiser for a quick test. > It is very useful for my work flow; > Just change some code and invoke "./MAKEALL -s uniphier" > I can test local changes without commiting them. > > > In buildman, I need to commit the local changes once and do > git branch --set-upstream-to <upstream-branch> > tools/buildman/buildman -b <topic-branch> > which requires me lots of typing.
OK thanks for pointing that out. That feature existed in an early pre-submission version of buildman but I dropped it. I'll see if I can implement ti again. Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
