Hi Wolfgang,
On 22 October 2014 11:56, Wolfgang Denk wd@denx.de wrote:
Dear Simon,
In message <CAPnjgZ2ZmGiQoi-mKQxK0vNPCs3hhqgk= z5CxbfSUm8LjU2kNA@mail.gmail.com> you wrote:
My concern is that we'll get people complaining about things not being mapped back exactly right. For example, MAKEALL am335x_evm builds one board, am335x_evm_config but buildman am335x_evm builds the whole
family
of configs. For a build test bisect run, that's fine (even if not optimal in that it'll build more than required). In fact if I read things right (Simon?) buildman is bad for a single board/config.
This is one of my open questions with buildman, too. Simon?
Yes it does a substring match. I'm open to suggestions on this though. It actually supports regular expressions.
So something like
buildman '^am335x_evm$'would work?
Yes:
$ ./tools/buildman/buildman -s am335x_evm -n boards.cfg is up to date. Nothing to do. Dry run, so not doing much. But I would do this:
Building current source for 5 boards (4 threads, 1 job per thread) Build directory: ../current
am335x_evm : 5 boards Total boards to build for each commit: 5
$ ./tools/buildman/buildman -s am335x_evm$ -n boards.cfg is up to date. Nothing to do. Dry run, so not doing much. But I would do this:
Building current source for 1 boards (1 thread, 4 jobs per thread) Build directory: ../current
am335x_evm$ : 1 boards Total boards to build for each commit: 1
Regards, Simon