diff options
author | Simon Glass <sjg@chromium.org> | 2014-08-09 15:33:08 -0600 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2014-08-13 08:34:16 -0600 |
commit | 6131beab6993f29bd6e52e94180654cb759dc4c7 (patch) | |
tree | 2501109cf27607293985f58fd502d301a93a4594 /tools/buildman/README | |
parent | e9569478582ba8b524a9e21f95ca339d271b1f41 (diff) | |
download | u-boot-imx-6131beab6993f29bd6e52e94180654cb759dc4c7.zip u-boot-imx-6131beab6993f29bd6e52e94180654cb759dc4c7.tar.gz u-boot-imx-6131beab6993f29bd6e52e94180654cb759dc4c7.tar.bz2 |
buildman: Introduce an 'and' operator for board selection
Currently buildman allows a list of boards to build to be specified on the
command line. The list can include specific board names, architecture, SOC
and so on.
At present the list of boards is dealt with in an 'OR' fashion, and there
is no way to specify something like 'arm & freescale', meaning boards with
ARM architecture but only those made by Freescale. This would exclude the
PowerPC boards made by Freescale.
Support an '&' operator on the command line to permit this. Ensure that
arguments can be specified in a single string to permit easy shell quoting.
Suggested-by: York Sun <yorksun@freescale.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
Acked-by: York Sun <yorksun@freescale.com>
Diffstat (limited to 'tools/buildman/README')
-rw-r--r-- | tools/buildman/README | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/tools/buildman/README b/tools/buildman/README index aaf0a10..d4e8404 100644 --- a/tools/buildman/README +++ b/tools/buildman/README @@ -108,6 +108,15 @@ behaviour is a superset of exact or substring matching. Examples are: * '^tegra[23]0$' All boards with either Tegra20 or Tegra30 SoC * 'powerpc' All PowerPC boards +While the default is to OR the terms together, you can also make use of +the '&' operator to limit the selection: + +* 'freescale & arm sandbox' All Freescale boards with ARM architecture, + plus sandbox + +It is convenient to use the -n option to see whaat will be built based on +the subset given. + Buildman does not store intermediate object files. It optionally copies the binary output into a directory when a build is successful. Size information is always recorded. It needs a fair bit of disk space to work, |