2009-12-07 05:58:28 +00:00
|
|
|
#!/bin/bash
|
2010-10-17 10:26:48 +00:00
|
|
|
# Tool mainly for U-Boot Quality Assurance: build one or more board
|
|
|
|
# configurations with minimal verbosity, showing only warnings and
|
|
|
|
# errors.
|
Licenses: introduce SPDX Unique Lincense Identifiers
Like many other projects, U-Boot has a tradition of including big
blocks of License headers in all files. This not only blows up the
source code with mostly redundant information, but also makes it very
difficult to generate License Clearing Reports. An additional problem
is that even the same lincenses are referred to by a number of
slightly varying text blocks (full, abbreviated, different
indentation, line wrapping and/or white space, with obsolete address
information, ...) which makes automatic processing a nightmare.
To make this easier, such license headers in the source files will be
replaced with a single line reference to Unique Lincense Identifiers
as defined by the Linux Foundation's SPDX project [1]. For example,
in a source file the full "GPL v2.0 or later" header text will be
replaced by a single line:
SPDX-License-Identifier: GPL-2.0+
We use the SPDX Unique Lincense Identifiers here; these are available
at [2].
Note: From the legal point of view, this patch is supposed to be only
a change to the textual representation of the license information,
but in no way any change to the actual license terms. With this patch
applied, all files will still be licensed under the same terms they
were before.
Note 2: The apparent difference between the old "COPYING" and the new
"Licenses/gpl-2.0.txt" only results from switching to the upstream
version of the license which is differently formatted; there are not
any actual changes to the content.
Note 3: There are some recurring questions about linense issues, such
as:
- Is a "All Rights Reserved" clause a problem in GPL code?
- Are files without any license header a problem?
- Do we need license headers at all?
The following excerpt from an e-mail by Daniel B. Ravicher should help
with these:
| Message-ID: <4ADF8CAA.5030808@softwarefreedom.org>
| Date: Wed, 21 Oct 2009 18:35:22 -0400
| From: "Daniel B. Ravicher" <ravicher@softwarefreedom.org>
| To: Wolfgang Denk <wd@denx.de>
| Subject: Re: GPL and license cleanup questions
|
| Mr. Denk,
|
| Wolfgang Denk wrote:
| > - There are a number of files which do not include any specific
| > license information at all. Is it correct to assume that these files
| > are automatically covered by the "GPL v2 or later" clause as
| > specified by the COPYING file in the top level directory of the
| > U-Boot source tree?
|
| That is a very fact specific analysis and could be different across the
| various files. However, if the contributor could reasonably be expected
| to have known that the project was licensed GPLv2 or later at the time
| she made her contribution, then a reasonably implication is that she
| consented to her contributions being distributed under those terms.
|
| > - Do such files need any clean up, for example should we add GPL
| > headers to them, or is this not needed?
|
| If the project as a whole is licensed under clear terms, you need not
| identify those same terms in each file, although there is no harm in
| doing so.
|
| > - There are other files, which include both a GPL license header
| > _plus_ some copyright note with an "All Rights Reserved" clause. It
| > has been my understanding that this is a conflict, and me must ask
| > the copyright holders to remove such "All Rights Reserved" clauses.
| > But then, some people claim that "All Rights Reserved" is a no-op
| > nowadays. License checking tools (like OSLC) seem to indicate this is
| > a problem, but then we see quite a lot of "All rights reserved" in
| > BSD-licensed files in gcc and glibc. So what is the correct way to
| > deal with such files?
|
| It is not a conflict to grant a license and also reserve all rights, as
| implicit in that language is that you are reserving all "other" rights
| not granted in the license. Thus, a file with "Licensed under GPL, All
| Rights Reserved" would mean that it is licensed under the GPL, but no
| other rights are given to copy, modify or redistribute it.
|
| Warm regards,
| --Dan
|
| Daniel B. Ravicher, Legal Director
| Software Freedom Law Center (SFLC) and Moglen Ravicher LLC
| 1995 Broadway, 17th Fl., New York, NY 10023
| (212) 461-1902 direct (212) 580-0800 main (212) 580-0898 fax
| ravicher@softwarefreedom.org www.softwarefreedom.org
[1] http://spdx.org/
[2] http://spdx.org/licenses/
Signed-off-by: Wolfgang Denk <wd@denx.de>
2013-06-21 08:22:36 +00:00
|
|
|
#
|
|
|
|
# SPDX-License-Identifier: GPL-2.0+
|
2010-10-17 10:26:48 +00:00
|
|
|
|
2011-04-21 22:01:43 +00:00
|
|
|
usage()
|
|
|
|
{
|
|
|
|
# if exiting with 0, write to stdout, else write to stderr
|
|
|
|
local ret=${1:-0}
|
|
|
|
[ "${ret}" -eq 1 ] && exec 1>&2
|
|
|
|
cat <<-EOF
|
|
|
|
Usage: MAKEALL [options] [--] [boards-to-build]
|
|
|
|
|
|
|
|
Options:
|
|
|
|
-a ARCH, --arch ARCH Build all boards with arch ARCH
|
|
|
|
-c CPU, --cpu CPU Build all boards with cpu CPU
|
|
|
|
-v VENDOR, --vendor VENDOR Build all boards with vendor VENDOR
|
|
|
|
-s SOC, --soc SOC Build all boards with soc SOC
|
2013-11-21 10:06:58 +00:00
|
|
|
-b BOARD, --board BOARD Build all boards with board name BOARD
|
2011-12-02 21:32:03 +00:00
|
|
|
-l, --list List all targets to be built
|
2012-03-05 15:10:51 +00:00
|
|
|
-m, --maintainers List all targets and maintainer email
|
|
|
|
-M, --mails List all targets and all affilated emails
|
2012-09-27 14:57:34 +00:00
|
|
|
-C, --check Enable build checking
|
2012-10-30 15:55:21 +00:00
|
|
|
-n, --continue Continue (skip boards already built)
|
|
|
|
-r, --rebuild-errors Rebuild any boards that errored
|
2011-04-21 22:01:43 +00:00
|
|
|
-h, --help This help output
|
|
|
|
|
|
|
|
Selections by these options are logically ANDed; if the same option
|
|
|
|
is used repeatedly, such selections are ORed. So "-v FOO -v BAR"
|
|
|
|
will select all configurations where the vendor is either FOO or
|
|
|
|
BAR. Any additional arguments specified on the command line are
|
|
|
|
always build additionally. See the boards.cfg file for more info.
|
|
|
|
|
|
|
|
If no boards are specified, then the default is "powerpc".
|
|
|
|
|
|
|
|
Environment variables:
|
|
|
|
BUILD_NCPUS number of parallel make jobs (default: auto)
|
|
|
|
CROSS_COMPILE cross-compiler toolchain prefix (default: "")
|
2013-01-29 14:34:58 +00:00
|
|
|
CROSS_COMPILE_<ARCH> cross-compiler toolchain prefix for
|
2013-10-04 15:43:24 +00:00
|
|
|
architecture "ARCH". Substitute "ARCH" for any
|
|
|
|
supported architecture (default: "")
|
2011-04-21 22:01:43 +00:00
|
|
|
MAKEALL_LOGDIR output all logs to here (default: ./LOG/)
|
|
|
|
BUILD_DIR output build directory (default: ./)
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
BUILD_NBUILDS number of parallel targets (default: 1)
|
2011-04-21 22:01:43 +00:00
|
|
|
|
|
|
|
Examples:
|
|
|
|
- build all Power Architecture boards:
|
|
|
|
MAKEALL -a powerpc
|
|
|
|
MAKEALL --arch powerpc
|
|
|
|
MAKEALL powerpc
|
|
|
|
- build all PowerPC boards manufactured by vendor "esd":
|
|
|
|
MAKEALL -a powerpc -v esd
|
|
|
|
- build all PowerPC boards manufactured either by "keymile" or "siemens":
|
|
|
|
MAKEALL -a powerpc -v keymile -v siemens
|
|
|
|
- build all Freescale boards with MPC83xx CPUs, plus all 4xx boards:
|
|
|
|
MAKEALL -c mpc83xx -v freescale 4xx
|
|
|
|
EOF
|
|
|
|
exit ${ret}
|
|
|
|
}
|
|
|
|
|
2013-11-21 10:06:58 +00:00
|
|
|
SHORT_OPTS="ha:c:v:s:b:lmMCnr"
|
|
|
|
LONG_OPTS="help,arch:,cpu:,vendor:,soc:,board:,list,maintainers,mails,check,continue,rebuild-errors"
|
2010-10-17 10:26:48 +00:00
|
|
|
|
|
|
|
# Option processing based on util-linux-2.13/getopt-parse.bash
|
|
|
|
|
2010-10-27 20:48:30 +00:00
|
|
|
# Note that we use `"$@"' to let each command-line parameter expand to a
|
2010-10-17 10:26:48 +00:00
|
|
|
# separate word. The quotes around `$@' are essential!
|
|
|
|
# We need TEMP as the `eval set --' would nuke the return value of
|
|
|
|
# getopt.
|
|
|
|
TEMP=`getopt -o ${SHORT_OPTS} --long ${LONG_OPTS} \
|
|
|
|
-n 'MAKEALL' -- "$@"`
|
|
|
|
|
2011-04-21 22:01:43 +00:00
|
|
|
[ $? != 0 ] && usage 1
|
2010-10-17 10:26:48 +00:00
|
|
|
|
|
|
|
# Note the quotes around `$TEMP': they are essential!
|
|
|
|
eval set -- "$TEMP"
|
|
|
|
|
|
|
|
SELECTED=''
|
2011-12-02 21:32:03 +00:00
|
|
|
ONLY_LIST=''
|
2012-03-05 15:10:51 +00:00
|
|
|
PRINT_MAINTS=''
|
|
|
|
MAINTAINERS_ONLY=''
|
2012-10-30 15:55:21 +00:00
|
|
|
CONTINUE=''
|
|
|
|
REBUILD_ERRORS=''
|
2010-10-17 10:26:48 +00:00
|
|
|
|
|
|
|
while true ; do
|
|
|
|
case "$1" in
|
|
|
|
-a|--arch)
|
|
|
|
# echo "Option ARCH: argument \`$2'"
|
|
|
|
if [ "$opt_a" ] ; then
|
|
|
|
opt_a="${opt_a%)} || \$2 == \"$2\")"
|
|
|
|
else
|
|
|
|
opt_a="(\$2 == \"$2\")"
|
|
|
|
fi
|
|
|
|
SELECTED='y'
|
|
|
|
shift 2 ;;
|
|
|
|
-c|--cpu)
|
|
|
|
# echo "Option CPU: argument \`$2'"
|
|
|
|
if [ "$opt_c" ] ; then
|
2012-08-31 08:30:06 +00:00
|
|
|
opt_c="${opt_c%)} || \$3 == \"$2\" || \$3 ~ /$2:/)"
|
2010-10-17 10:26:48 +00:00
|
|
|
else
|
2012-08-31 08:30:06 +00:00
|
|
|
opt_c="(\$3 == \"$2\" || \$3 ~ /$2:/)"
|
2010-10-17 10:26:48 +00:00
|
|
|
fi
|
|
|
|
SELECTED='y'
|
|
|
|
shift 2 ;;
|
|
|
|
-s|--soc)
|
|
|
|
# echo "Option SoC: argument \`$2'"
|
|
|
|
if [ "$opt_s" ] ; then
|
2013-09-11 13:52:51 +00:00
|
|
|
opt_s="${opt_s%)} || \$4 == \"$2\" || \$4 ~ /$2/)"
|
2010-10-17 10:26:48 +00:00
|
|
|
else
|
2013-09-11 13:52:51 +00:00
|
|
|
opt_s="(\$4 == \"$2\" || \$4 ~ /$2/)"
|
2010-10-17 10:26:48 +00:00
|
|
|
fi
|
|
|
|
SELECTED='y'
|
|
|
|
shift 2 ;;
|
|
|
|
-v|--vendor)
|
|
|
|
# echo "Option VENDOR: argument \`$2'"
|
|
|
|
if [ "$opt_v" ] ; then
|
|
|
|
opt_v="${opt_v%)} || \$5 == \"$2\")"
|
|
|
|
else
|
|
|
|
opt_v="(\$5 == \"$2\")"
|
|
|
|
fi
|
|
|
|
SELECTED='y'
|
|
|
|
shift 2 ;;
|
2013-11-21 10:06:58 +00:00
|
|
|
-b|--board)
|
|
|
|
# echo "Option BOARD: argument \`$2'"
|
|
|
|
if [ "$opt_b" ] ; then
|
|
|
|
opt_b="${opt_b%)} || \$6 == \"$2\" || \$7 == \"$2\")"
|
|
|
|
else
|
|
|
|
# We need to check the 7th field too
|
|
|
|
# for boards whose 6th field is "-"
|
|
|
|
opt_b="(\$6 == \"$2\" || \$7 == \"$2\")"
|
|
|
|
fi
|
|
|
|
SELECTED='y'
|
|
|
|
shift 2 ;;
|
2012-09-27 14:57:34 +00:00
|
|
|
-C|--check)
|
|
|
|
CHECK='C=1'
|
|
|
|
shift ;;
|
2012-10-30 15:55:21 +00:00
|
|
|
-n|--continue)
|
|
|
|
CONTINUE='y'
|
|
|
|
shift ;;
|
|
|
|
-r|--rebuild-errors)
|
|
|
|
REBUILD_ERRORS='y'
|
|
|
|
shift ;;
|
2011-12-02 21:32:03 +00:00
|
|
|
-l|--list)
|
|
|
|
ONLY_LIST='y'
|
|
|
|
shift ;;
|
2012-03-05 15:10:51 +00:00
|
|
|
-m|--maintainers)
|
|
|
|
ONLY_LIST='y'
|
|
|
|
PRINT_MAINTS='y'
|
|
|
|
MAINTAINERS_ONLY='y'
|
|
|
|
shift ;;
|
|
|
|
-M|--mails)
|
|
|
|
ONLY_LIST='y'
|
|
|
|
PRINT_MAINTS='y'
|
|
|
|
shift ;;
|
2011-04-21 22:01:43 +00:00
|
|
|
-h|--help)
|
|
|
|
usage ;;
|
2010-10-17 10:26:48 +00:00
|
|
|
--)
|
|
|
|
shift ; break ;;
|
|
|
|
*)
|
|
|
|
echo "Internal error!" >&2 ; exit 1 ;;
|
|
|
|
esac
|
|
|
|
done
|
2014-07-22 02:19:08 +00:00
|
|
|
|
|
|
|
GNU_MAKE=$(scripts/show-gnu-make) || {
|
|
|
|
echo "GNU Make not found" >&2
|
|
|
|
exit 1
|
|
|
|
}
|
|
|
|
|
2010-10-17 10:26:48 +00:00
|
|
|
# echo "Remaining arguments:"
|
|
|
|
# for arg do echo '--> '"\`$arg'" ; done
|
|
|
|
|
2014-07-30 05:08:21 +00:00
|
|
|
if [ ! -r boards.cfg ]; then
|
|
|
|
echo "Could not find boards.cfg"
|
|
|
|
tools/genboardscfg.py || {
|
|
|
|
echo "Failed to generate boards.cfg" >&2
|
|
|
|
exit 1
|
|
|
|
}
|
|
|
|
fi
|
|
|
|
|
2010-10-17 10:26:48 +00:00
|
|
|
FILTER="\$1 !~ /^#/"
|
|
|
|
[ "$opt_a" ] && FILTER="${FILTER} && $opt_a"
|
|
|
|
[ "$opt_c" ] && FILTER="${FILTER} && $opt_c"
|
|
|
|
[ "$opt_s" ] && FILTER="${FILTER} && $opt_s"
|
|
|
|
[ "$opt_v" ] && FILTER="${FILTER} && $opt_v"
|
2013-11-21 10:06:58 +00:00
|
|
|
[ "$opt_b" ] && FILTER="${FILTER} && $opt_b"
|
2010-10-17 10:26:48 +00:00
|
|
|
|
|
|
|
if [ "$SELECTED" ] ; then
|
2013-09-11 13:52:51 +00:00
|
|
|
SELECTED=$(awk '('"$FILTER"') { print $7 }' boards.cfg)
|
2010-10-29 22:59:06 +00:00
|
|
|
|
|
|
|
# Make sure some boards from boards.cfg are actually found
|
|
|
|
if [ -z "$SELECTED" ] ; then
|
|
|
|
echo "Error: No boards selected, invalid arguments"
|
|
|
|
exit 1
|
|
|
|
fi
|
2010-10-17 10:26:48 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
#########################################################################
|
|
|
|
|
2009-09-21 17:04:32 +00:00
|
|
|
# Print statistics when we exit
|
|
|
|
trap exit 1 2 3 15
|
|
|
|
trap print_stats 0
|
|
|
|
|
2008-12-08 23:39:08 +00:00
|
|
|
# Determine number of CPU cores if no default was set
|
|
|
|
: ${BUILD_NCPUS:="`getconf _NPROCESSORS_ONLN`"}
|
|
|
|
|
|
|
|
if [ "$BUILD_NCPUS" -gt 1 ]
|
|
|
|
then
|
2009-09-21 17:04:33 +00:00
|
|
|
JOBS="-j $((BUILD_NCPUS + 1))"
|
2008-12-08 23:39:08 +00:00
|
|
|
else
|
|
|
|
JOBS=""
|
|
|
|
fi
|
|
|
|
|
2006-09-01 17:49:50 +00:00
|
|
|
if [ "${MAKEALL_LOGDIR}" ] ; then
|
|
|
|
LOG_DIR=${MAKEALL_LOGDIR}
|
|
|
|
else
|
|
|
|
LOG_DIR="LOG"
|
|
|
|
fi
|
2006-09-07 09:51:23 +00:00
|
|
|
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
: ${BUILD_NBUILDS:=1}
|
|
|
|
BUILD_MANY=0
|
|
|
|
|
|
|
|
if [ "${BUILD_NBUILDS}" -gt 1 ] ; then
|
|
|
|
BUILD_MANY=1
|
|
|
|
: ${BUILD_DIR:=./build}
|
|
|
|
mkdir -p "${BUILD_DIR}/ERR"
|
|
|
|
find "${BUILD_DIR}/ERR/" -type f -exec rm -f {} +
|
2006-09-01 17:49:50 +00:00
|
|
|
fi
|
|
|
|
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
: ${BUILD_DIR:=.}
|
|
|
|
|
|
|
|
OUTPUT_PREFIX="${BUILD_DIR}"
|
|
|
|
|
|
|
|
[ -d ${LOG_DIR} ] || mkdir "${LOG_DIR}" || exit 1
|
2012-10-30 15:55:21 +00:00
|
|
|
if [ "$CONTINUE" != 'y' -a "$REBUILD_ERRORS" != 'y' ] ; then
|
|
|
|
find "${LOG_DIR}/" -type f -exec rm -f {} +
|
|
|
|
fi
|
2002-11-02 23:17:16 +00:00
|
|
|
|
|
|
|
LIST=""
|
|
|
|
|
2009-09-21 17:04:32 +00:00
|
|
|
# Keep track of the number of builds and errors
|
|
|
|
ERR_CNT=0
|
|
|
|
ERR_LIST=""
|
2012-05-21 04:49:38 +00:00
|
|
|
WRN_CNT=0
|
|
|
|
WRN_LIST=""
|
2009-09-21 17:04:32 +00:00
|
|
|
TOTAL_CNT=0
|
2012-10-30 15:55:21 +00:00
|
|
|
SKIP_CNT=0
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
CURRENT_CNT=0
|
|
|
|
OLDEST_IDX=1
|
2009-12-07 05:58:28 +00:00
|
|
|
RC=0
|
2009-09-21 17:04:32 +00:00
|
|
|
|
2010-08-19 17:05:06 +00:00
|
|
|
# Helper funcs for parsing boards.cfg
|
2013-10-21 02:11:28 +00:00
|
|
|
targets_by_field()
|
2010-08-19 17:05:06 +00:00
|
|
|
{
|
2013-10-21 02:11:27 +00:00
|
|
|
field=$1
|
|
|
|
regexp=$2
|
|
|
|
|
|
|
|
awk '($1 !~ /^#/ && $'"$field"' ~ /^'"$regexp"'$/) { print $7 }' \
|
|
|
|
boards.cfg
|
2010-08-19 17:05:06 +00:00
|
|
|
}
|
2013-10-21 02:11:27 +00:00
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
targets_by_arch() { targets_by_field 2 "$@" ; }
|
|
|
|
targets_by_cpu() { targets_by_field 3 "$@" ; targets_by_field 3 "$@:.*" ; }
|
|
|
|
targets_by_soc() { targets_by_field 4 "$@" ; }
|
2010-08-19 17:05:06 +00:00
|
|
|
|
2003-03-31 17:27:09 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC5xx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_5xx="$(targets_by_cpu mpc5xx)"
|
2003-03-31 17:27:09 +00:00
|
|
|
|
2003-07-16 21:53:01 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC5xxx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_5xxx="$(targets_by_cpu mpc5xxx)"
|
2003-07-16 21:53:01 +00:00
|
|
|
|
2007-07-27 12:43:59 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC512x Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_512x="$(targets_by_cpu mpc512x)"
|
2003-07-16 21:53:01 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC8xx Systems
|
|
|
|
#########################################################################
|
2010-08-19 17:05:06 +00:00
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_8xx="$(targets_by_cpu mpc8xx)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
|
|
|
#########################################################################
|
|
|
|
## PPC4xx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_4xx="$(targets_by_cpu ppc4xx)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
|
|
|
#########################################################################
|
|
|
|
## MPC824x Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_824x="$(targets_by_cpu mpc824x)"
|
2003-06-21 00:17:24 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
2003-05-03 15:50:43 +00:00
|
|
|
## MPC8260 Systems (includes 8250, 8255 etc.)
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_8260="$(targets_by_cpu mpc8260)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2005-07-28 15:08:46 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC83xx Systems (includes 8349, etc.)
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_83xx="$(targets_by_cpu mpc83xx)"
|
2005-07-28 15:08:46 +00:00
|
|
|
|
2003-10-15 23:53:47 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC85xx Systems (includes 8540, 8560 etc.)
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_85xx="$(targets_by_cpu mpc85xx)"
|
2003-10-15 23:53:47 +00:00
|
|
|
|
2007-05-23 19:09:46 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC86xx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_86xx="$(targets_by_cpu mpc86xx)"
|
2007-05-23 19:09:46 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
## 74xx/7xx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_74xx_7xx="$(targets_by_cpu 74xx_7xx)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2008-04-20 22:35:52 +00:00
|
|
|
#########################################################################
|
|
|
|
## PowerPC groups
|
|
|
|
#########################################################################
|
|
|
|
|
|
|
|
LIST_TSEC=" \
|
|
|
|
${LIST_83xx} \
|
|
|
|
${LIST_85xx} \
|
|
|
|
${LIST_86xx} \
|
|
|
|
"
|
|
|
|
|
2010-04-15 14:07:28 +00:00
|
|
|
LIST_powerpc=" \
|
2007-08-10 20:34:48 +00:00
|
|
|
${LIST_5xx} \
|
2007-11-25 21:39:25 +00:00
|
|
|
${LIST_512x} \
|
2007-08-10 20:34:48 +00:00
|
|
|
${LIST_5xxx} \
|
|
|
|
${LIST_8xx} \
|
|
|
|
${LIST_824x} \
|
|
|
|
${LIST_8260} \
|
|
|
|
${LIST_83xx} \
|
|
|
|
${LIST_85xx} \
|
|
|
|
${LIST_86xx} \
|
|
|
|
${LIST_4xx} \
|
2010-10-06 07:05:45 +00:00
|
|
|
${LIST_74xx_7xx}\
|
2007-08-10 20:34:48 +00:00
|
|
|
"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2010-04-15 14:07:28 +00:00
|
|
|
# Alias "ppc" -> "powerpc" to not break compatibility with older scripts
|
|
|
|
# still using "ppc" instead of "powerpc"
|
|
|
|
LIST_ppc=" \
|
|
|
|
${LIST_powerpc} \
|
|
|
|
"
|
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
## StrongARM Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_SA="$(targets_by_cpu sa1100)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2012-08-29 11:08:59 +00:00
|
|
|
#########################################################################
|
|
|
|
## ARM7 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_ARM7="$(targets_by_cpu arm720t)"
|
2012-08-29 11:08:59 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
## ARM9 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_ARM9="$(targets_by_cpu arm920t) \
|
|
|
|
$(targets_by_cpu arm926ejs) \
|
|
|
|
$(targets_by_cpu arm946es) \
|
2003-08-29 22:00:43 +00:00
|
|
|
"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2005-01-09 23:16:25 +00:00
|
|
|
#########################################################################
|
|
|
|
## ARM11 Systems
|
|
|
|
#########################################################################
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_ARM11="$(targets_by_cpu arm1136) \
|
|
|
|
$(targets_by_cpu arm1176) \
|
2012-08-29 11:08:59 +00:00
|
|
|
"
|
2005-01-09 23:16:25 +00:00
|
|
|
|
2009-01-27 17:19:12 +00:00
|
|
|
#########################################################################
|
2010-06-18 04:50:01 +00:00
|
|
|
## ARMV7 Systems
|
2009-01-27 17:19:12 +00:00
|
|
|
#########################################################################
|
2011-08-05 20:48:32 +00:00
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_ARMV7="$(targets_by_cpu armv7)"
|
2009-01-27 17:19:12 +00:00
|
|
|
|
2013-12-14 03:47:38 +00:00
|
|
|
#########################################################################
|
|
|
|
## ARMV8 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
|
|
|
LIST_ARMV8="$(targets_by_cpu armv8)"
|
|
|
|
|
2008-05-24 10:47:46 +00:00
|
|
|
#########################################################################
|
|
|
|
## AT91 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_at91="$(targets_by_soc at91)"
|
2008-05-24 10:47:46 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
## Xscale Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_pxa="$(targets_by_cpu pxa)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2012-05-30 22:59:43 +00:00
|
|
|
#########################################################################
|
|
|
|
## SPEAr Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_spear="$(targets_by_soc spear)"
|
2012-05-30 22:59:43 +00:00
|
|
|
|
2008-04-20 22:35:52 +00:00
|
|
|
#########################################################################
|
|
|
|
## ARM groups
|
|
|
|
#########################################################################
|
2003-10-14 19:43:55 +00:00
|
|
|
|
2013-12-14 03:47:38 +00:00
|
|
|
LIST_arm="$(targets_by_arch arm | \
|
|
|
|
for ARMV8_TARGET in $LIST_ARMV8; \
|
|
|
|
do sed "/$ARMV8_TARGET/d"; \
|
|
|
|
done) \
|
|
|
|
"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2003-03-27 12:09:35 +00:00
|
|
|
#########################################################################
|
2005-08-13 22:27:00 +00:00
|
|
|
## MIPS Systems (default = big endian)
|
2003-03-27 12:09:35 +00:00
|
|
|
#########################################################################
|
|
|
|
|
2014-04-17 19:45:59 +00:00
|
|
|
LIST_mips="$(targets_by_arch mips)"
|
2003-03-27 12:09:35 +00:00
|
|
|
|
2011-11-18 19:21:37 +00:00
|
|
|
#########################################################################
|
|
|
|
## OpenRISC Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_openrisc="$(targets_by_arch openrisc)"
|
2005-08-13 22:27:00 +00:00
|
|
|
|
2003-05-31 18:35:21 +00:00
|
|
|
#########################################################################
|
2011-04-13 09:43:28 +00:00
|
|
|
## x86 Systems
|
2003-05-31 18:35:21 +00:00
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_x86="$(targets_by_arch x86)"
|
2003-05-31 18:35:21 +00:00
|
|
|
|
2004-10-10 21:27:30 +00:00
|
|
|
#########################################################################
|
|
|
|
## Nios-II Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_nios2="$(targets_by_arch nios2)"
|
2004-10-10 21:27:30 +00:00
|
|
|
|
2004-07-10 23:48:41 +00:00
|
|
|
#########################################################################
|
|
|
|
## MicroBlaze Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_microblaze="$(targets_by_arch microblaze)"
|
2004-07-10 23:48:41 +00:00
|
|
|
|
2006-01-26 22:38:46 +00:00
|
|
|
#########################################################################
|
|
|
|
## ColdFire Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_m68k="$(targets_by_arch m68k)"
|
2011-09-25 19:27:19 +00:00
|
|
|
LIST_coldfire=${LIST_m68k}
|
2006-01-26 22:38:46 +00:00
|
|
|
|
2006-10-24 12:42:37 +00:00
|
|
|
#########################################################################
|
|
|
|
## AVR32 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_avr32="$(targets_by_arch avr32)"
|
2006-10-24 12:42:37 +00:00
|
|
|
|
2007-03-09 05:40:56 +00:00
|
|
|
#########################################################################
|
|
|
|
## Blackfin Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_blackfin="$(targets_by_arch blackfin)"
|
2007-03-09 05:40:56 +00:00
|
|
|
|
2007-11-27 08:44:53 +00:00
|
|
|
#########################################################################
|
|
|
|
## SH Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_sh2="$(targets_by_cpu sh2)"
|
|
|
|
LIST_sh3="$(targets_by_cpu sh3)"
|
|
|
|
LIST_sh4="$(targets_by_cpu sh4)"
|
2008-04-20 22:35:52 +00:00
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_sh="$(targets_by_arch sh)"
|
2007-11-27 08:44:53 +00:00
|
|
|
|
2008-03-28 08:47:00 +00:00
|
|
|
#########################################################################
|
|
|
|
## SPARC Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_sparc="$(targets_by_arch sparc)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2011-10-19 20:41:10 +00:00
|
|
|
#########################################################################
|
|
|
|
## NDS32 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2013-10-21 02:11:28 +00:00
|
|
|
LIST_nds32="$(targets_by_arch nds32)"
|
2011-10-19 20:41:10 +00:00
|
|
|
|
2014-02-04 08:56:20 +00:00
|
|
|
#########################################################################
|
|
|
|
## ARC Systems
|
|
|
|
#########################################################################
|
|
|
|
|
|
|
|
LIST_arc="$(targets_by_arch arc)"
|
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#-----------------------------------------------------------------------
|
|
|
|
|
2012-03-05 15:10:51 +00:00
|
|
|
get_target_location() {
|
|
|
|
local target=$1
|
|
|
|
local BOARD_NAME=""
|
|
|
|
local CONFIG_NAME=""
|
|
|
|
local board=""
|
|
|
|
local vendor=""
|
|
|
|
|
|
|
|
# Automatic mode
|
2013-10-21 02:11:25 +00:00
|
|
|
local line=`awk '\$7 == "'"$target"'" { print \$0 }' boards.cfg`
|
2012-03-05 15:10:51 +00:00
|
|
|
if [ -z "${line}" ] ; then echo "" ; return ; fi
|
|
|
|
|
|
|
|
set ${line}
|
|
|
|
|
2014-07-30 05:08:21 +00:00
|
|
|
CONFIG_NAME="${7%_defconfig}"
|
2012-03-05 15:10:51 +00:00
|
|
|
|
2014-07-30 05:08:21 +00:00
|
|
|
[ "${BOARD_NAME}" ] || BOARD_NAME="${7%_defconfig}"
|
2012-03-05 15:10:51 +00:00
|
|
|
|
2013-09-11 13:52:51 +00:00
|
|
|
if [ $# -gt 5 ]; then
|
|
|
|
if [ "$6" = "-" ] ; then
|
|
|
|
board=${BOARD_NAME}
|
|
|
|
else
|
|
|
|
board="$6"
|
|
|
|
fi
|
2012-03-05 15:10:51 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
[ $# -gt 4 ] && [ "$5" != "-" ] && vendor="$5"
|
2013-09-11 13:52:51 +00:00
|
|
|
[ $# -gt 6 ] && [ "$8" != "-" ] && {
|
|
|
|
tmp="${8%:*}"
|
2012-03-05 15:10:51 +00:00
|
|
|
if [ "$tmp" ] ; then
|
|
|
|
CONFIG_NAME="$tmp"
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
|
|
|
# Assign board directory to BOARDIR variable
|
2013-09-11 13:52:51 +00:00
|
|
|
if [ "${vendor}" == "-" ] ; then
|
2012-03-05 15:10:51 +00:00
|
|
|
BOARDDIR=${board}
|
|
|
|
else
|
|
|
|
BOARDDIR=${vendor}/${board}
|
|
|
|
fi
|
|
|
|
|
2013-09-11 13:52:51 +00:00
|
|
|
echo "${CONFIG_NAME}:${BOARDDIR}:${BOARD_NAME}"
|
2012-03-05 15:10:51 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
get_target_maintainers() {
|
2013-09-11 13:52:51 +00:00
|
|
|
local name=`echo $1 | cut -d : -f 3`
|
2012-03-05 15:10:51 +00:00
|
|
|
|
2013-10-21 02:11:25 +00:00
|
|
|
local line=`awk '\$7 == "'"$target"'" { print \$0 }' boards.cfg`
|
2013-09-11 13:52:51 +00:00
|
|
|
if [ -z "${line}" ]; then
|
2012-03-05 15:10:51 +00:00
|
|
|
echo ""
|
|
|
|
return ;
|
|
|
|
fi
|
|
|
|
|
2013-09-11 13:52:51 +00:00
|
|
|
local mails=`echo ${line} | cut -d ' ' -f 9- | sed -e 's/[^<]*<//' -e 's/>.*</ /' -e 's/>[^>]*$//'`
|
|
|
|
[ "$mails" == "-" ] && mails=""
|
|
|
|
echo "$mails"
|
2012-03-05 15:10:51 +00:00
|
|
|
}
|
|
|
|
|
2013-01-29 14:34:58 +00:00
|
|
|
get_target_arch() {
|
|
|
|
local target=$1
|
|
|
|
|
|
|
|
# Automatic mode
|
2013-10-21 02:11:26 +00:00
|
|
|
local line=`awk '\$7 == "'"$target"'" { print \$0 }' boards.cfg`
|
2013-01-29 14:34:58 +00:00
|
|
|
|
|
|
|
if [ -z "${line}" ] ; then echo "" ; return ; fi
|
|
|
|
|
|
|
|
set ${line}
|
|
|
|
echo "$2"
|
|
|
|
}
|
|
|
|
|
2012-03-05 15:10:51 +00:00
|
|
|
list_target() {
|
|
|
|
if [ "$PRINT_MAINTS" != 'y' ] ; then
|
|
|
|
echo "$1"
|
|
|
|
return
|
|
|
|
fi
|
|
|
|
|
|
|
|
echo -n "$1:"
|
|
|
|
|
|
|
|
local loc=`get_target_location $1`
|
|
|
|
|
|
|
|
if [ -z "${loc}" ] ; then echo "ERROR" ; return ; fi
|
|
|
|
|
|
|
|
local maintainers_result=`get_target_maintainers ${loc} | tr " " "\n"`
|
|
|
|
|
|
|
|
if [ "$MAINTAINERS_ONLY" != 'y' ] ; then
|
|
|
|
|
|
|
|
local dir=`echo ${loc} | cut -d ":" -f 2`
|
|
|
|
local cfg=`echo ${loc} | cut -d ":" -f 1`
|
|
|
|
local git_result=`git log --format=%aE board/${dir} \
|
|
|
|
include/configs/${cfg}.h | grep "@"`
|
|
|
|
local git_result_recent=`echo ${git_result} | tr " " "\n" | \
|
|
|
|
head -n 3`
|
|
|
|
local git_result_top=`echo ${git_result} | tr " " "\n" | \
|
|
|
|
sort | uniq -c | sort -nr | head -n 3 | \
|
|
|
|
sed "s/^ \+[0-9]\+ \+//"`
|
|
|
|
|
|
|
|
echo -e "$git_result_recent\n$git_result_top\n$maintainers_result" | \
|
|
|
|
sort -u | tr "\n" " " | sed "s/ $//" ;
|
|
|
|
else
|
|
|
|
echo -e "$maintainers_result" | sort -u | tr "\n" " " | \
|
|
|
|
sed "s/ $//" ;
|
|
|
|
fi
|
|
|
|
|
|
|
|
echo ""
|
|
|
|
}
|
|
|
|
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
# Each finished build will have a file called ${donep}${n},
|
|
|
|
# where n is the index of the build. Each build
|
|
|
|
# we've already noted as finished will have ${skipp}${n}.
|
|
|
|
# The code managing the build process will use this information
|
|
|
|
# to ensure that only BUILD_NBUILDS builds are in flight at once
|
|
|
|
donep="${LOG_DIR}/._done_"
|
|
|
|
skipp="${LOG_DIR}/._skip_"
|
|
|
|
|
2012-10-30 15:55:20 +00:00
|
|
|
build_target_killed() {
|
|
|
|
echo "Aborted $target build."
|
|
|
|
# Remove the logs for this board since it was aborted
|
|
|
|
rm -f ${LOG_DIR}/$target.MAKELOG ${LOG_DIR}/$target.ERR
|
|
|
|
exit
|
|
|
|
}
|
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
build_target() {
|
|
|
|
target=$1
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
build_idx=$2
|
|
|
|
|
2012-05-09 20:36:28 +00:00
|
|
|
if [ "$ONLY_LIST" == 'y' ] ; then
|
|
|
|
list_target ${target}
|
|
|
|
return
|
|
|
|
fi
|
|
|
|
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
if [ $BUILD_MANY == 1 ] ; then
|
|
|
|
output_dir="${OUTPUT_PREFIX}/${target}"
|
|
|
|
mkdir -p "${output_dir}"
|
2012-10-30 15:55:20 +00:00
|
|
|
trap build_target_killed TERM
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
else
|
|
|
|
output_dir="${OUTPUT_PREFIX}"
|
|
|
|
fi
|
|
|
|
|
2013-01-29 14:34:58 +00:00
|
|
|
target_arch=$(get_target_arch ${target})
|
2013-03-22 07:37:03 +00:00
|
|
|
eval cross_toolchain=\$CROSS_COMPILE_`echo $target_arch | tr '[:lower:]' '[:upper:]'`
|
2013-01-29 14:34:58 +00:00
|
|
|
if [ "${cross_toolchain}" ] ; then
|
2014-07-22 02:19:08 +00:00
|
|
|
MAKE="$GNU_MAKE CROSS_COMPILE=${cross_toolchain}"
|
2013-01-29 14:34:58 +00:00
|
|
|
elif [ "${CROSS_COMPILE}" ] ; then
|
2014-07-22 02:19:08 +00:00
|
|
|
MAKE="$GNU_MAKE CROSS_COMPILE=${CROSS_COMPILE}"
|
2013-01-29 14:34:58 +00:00
|
|
|
else
|
2014-07-22 02:19:08 +00:00
|
|
|
MAKE=$GNU_MAKE
|
2013-01-29 14:34:58 +00:00
|
|
|
fi
|
|
|
|
|
2014-02-04 08:24:24 +00:00
|
|
|
if [ "${output_dir}" != "." ] ; then
|
|
|
|
MAKE="${MAKE} O=${output_dir}"
|
|
|
|
fi
|
|
|
|
|
2014-08-20 20:10:29 +00:00
|
|
|
${MAKE} mrproper >/dev/null
|
2014-07-30 05:08:21 +00:00
|
|
|
|
|
|
|
echo "Building ${target} board..."
|
|
|
|
${MAKE} -s ${target}_defconfig >/dev/null
|
2006-09-01 17:49:50 +00:00
|
|
|
|
2012-09-27 14:57:34 +00:00
|
|
|
${MAKE} ${JOBS} ${CHECK} all \
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
>${LOG_DIR}/$target.MAKELOG 2> ${LOG_DIR}/$target.ERR
|
2009-12-07 05:58:28 +00:00
|
|
|
|
|
|
|
# Check for 'make' errors
|
|
|
|
if [ ${PIPESTATUS[0]} -ne 0 ] ; then
|
|
|
|
RC=1
|
|
|
|
fi
|
|
|
|
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
if [ $BUILD_MANY == 1 ] ; then
|
2012-10-30 15:55:20 +00:00
|
|
|
trap - TERM
|
|
|
|
|
2014-02-04 08:24:34 +00:00
|
|
|
${MAKE} -s clean
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
|
|
|
|
if [ -s ${LOG_DIR}/${target}.ERR ] ; then
|
2012-05-21 04:49:38 +00:00
|
|
|
cp ${LOG_DIR}/${target}.ERR ${OUTPUT_PREFIX}/ERR/${target}
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
else
|
|
|
|
rm ${LOG_DIR}/${target}.ERR
|
|
|
|
fi
|
2009-09-21 17:04:32 +00:00
|
|
|
else
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
if [ -s ${LOG_DIR}/${target}.ERR ] ; then
|
2012-05-21 04:49:38 +00:00
|
|
|
if grep -iw error ${LOG_DIR}/${target}.ERR ; then
|
|
|
|
: $(( ERR_CNT += 1 ))
|
|
|
|
ERR_LIST="${ERR_LIST} $target"
|
|
|
|
else
|
|
|
|
: $(( WRN_CNT += 1 ))
|
|
|
|
WRN_LIST="${WRN_LIST} $target"
|
|
|
|
fi
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
else
|
|
|
|
rm ${LOG_DIR}/${target}.ERR
|
|
|
|
fi
|
2009-09-21 17:04:32 +00:00
|
|
|
fi
|
|
|
|
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
OBJS=${output_dir}/u-boot
|
|
|
|
if [ -e ${output_dir}/spl/u-boot-spl ]; then
|
|
|
|
OBJS="${OBJS} ${output_dir}/spl/u-boot-spl"
|
2012-02-20 12:56:25 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
${CROSS_COMPILE}size ${OBJS} | tee -a ${LOG_DIR}/$target.MAKELOG
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
|
|
|
|
[ -e "${LOG_DIR}/${target}.ERR" ] && cat "${LOG_DIR}/${target}.ERR"
|
|
|
|
|
|
|
|
touch "${donep}${build_idx}"
|
2002-11-02 23:17:16 +00:00
|
|
|
}
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
|
|
|
|
manage_builds() {
|
|
|
|
search_idx=${OLDEST_IDX}
|
2012-05-09 20:36:28 +00:00
|
|
|
if [ "$ONLY_LIST" == 'y' ] ; then return ; fi
|
|
|
|
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
while true; do
|
|
|
|
if [ -e "${donep}${search_idx}" ] ; then
|
|
|
|
: $(( CURRENT_CNT-- ))
|
|
|
|
[ ${OLDEST_IDX} -eq ${search_idx} ] &&
|
|
|
|
: $(( OLDEST_IDX++ ))
|
|
|
|
|
|
|
|
# Only want to count it once
|
|
|
|
rm -f "${donep}${search_idx}"
|
|
|
|
touch "${skipp}${search_idx}"
|
|
|
|
elif [ -e "${skipp}${search_idx}" ] ; then
|
|
|
|
[ ${OLDEST_IDX} -eq ${search_idx} ] &&
|
|
|
|
: $(( OLDEST_IDX++ ))
|
|
|
|
fi
|
|
|
|
: $(( search_idx++ ))
|
|
|
|
if [ ${search_idx} -gt ${TOTAL_CNT} ] ; then
|
|
|
|
if [ ${CURRENT_CNT} -ge ${BUILD_NBUILDS} ] ; then
|
|
|
|
search_idx=${OLDEST_IDX}
|
|
|
|
sleep 1
|
|
|
|
else
|
|
|
|
break
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
}
|
|
|
|
|
2010-08-19 17:05:06 +00:00
|
|
|
build_targets() {
|
|
|
|
for t in "$@" ; do
|
|
|
|
# If a LIST_xxx var exists, use it. But avoid variable
|
|
|
|
# expansion in the eval when a board name contains certain
|
|
|
|
# characters that the shell interprets.
|
|
|
|
case ${t} in
|
|
|
|
*[-+=]*) list= ;;
|
|
|
|
*) list=$(eval echo '${LIST_'$t'}') ;;
|
|
|
|
esac
|
|
|
|
if [ -n "${list}" ] ; then
|
|
|
|
build_targets ${list}
|
|
|
|
else
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
: $((TOTAL_CNT += 1))
|
|
|
|
: $((CURRENT_CNT += 1))
|
|
|
|
rm -f "${donep}${TOTAL_CNT}"
|
|
|
|
rm -f "${skipp}${TOTAL_CNT}"
|
2012-10-30 15:55:21 +00:00
|
|
|
if [ "$CONTINUE" = 'y' -a -e ${LOG_DIR}/$t.MAKELOG ] ; then
|
|
|
|
: $((SKIP_CNT += 1))
|
|
|
|
touch "${donep}${TOTAL_CNT}"
|
|
|
|
elif [ "$REBUILD_ERRORS" = 'y' -a ! -e ${LOG_DIR}/$t.ERR ] ; then
|
|
|
|
: $((SKIP_CNT += 1))
|
|
|
|
touch "${donep}${TOTAL_CNT}"
|
2012-05-21 04:49:37 +00:00
|
|
|
else
|
2012-10-30 15:55:21 +00:00
|
|
|
if [ $BUILD_MANY == 1 ] ; then
|
|
|
|
build_target ${t} ${TOTAL_CNT} &
|
|
|
|
else
|
|
|
|
CUR_TGT="${t}"
|
|
|
|
build_target ${t} ${TOTAL_CNT}
|
|
|
|
CUR_TGT=''
|
|
|
|
fi
|
2012-05-21 04:49:37 +00:00
|
|
|
fi
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
# We maintain a running count of all the builds we have done.
|
|
|
|
# Each finished build will have a file called ${donep}${n},
|
|
|
|
# where n is the index of the build. Each build
|
|
|
|
# we've already noted as finished will have ${skipp}${n}.
|
|
|
|
# We track the current index via TOTAL_CNT, and the oldest
|
|
|
|
# index. When we exceed the maximum number of parallel builds,
|
|
|
|
# We look from oldest to current for builds that have completed,
|
|
|
|
# and update the current count and oldest index as appropriate.
|
|
|
|
# If we've gone through the entire list, wait a second, and
|
|
|
|
# reprocess the entire list until we find a build that has
|
|
|
|
# completed
|
|
|
|
if [ ${CURRENT_CNT} -ge ${BUILD_NBUILDS} ] ; then
|
|
|
|
manage_builds
|
2010-08-19 17:05:06 +00:00
|
|
|
fi
|
|
|
|
done
|
|
|
|
}
|
2002-11-02 23:17:16 +00:00
|
|
|
|
|
|
|
#-----------------------------------------------------------------------
|
|
|
|
|
2012-05-09 20:36:28 +00:00
|
|
|
kill_children() {
|
2013-02-07 22:35:57 +00:00
|
|
|
local OS=$(uname -s)
|
|
|
|
local children=""
|
|
|
|
case "${OS}" in
|
|
|
|
"Darwin")
|
|
|
|
# Mac OS X is known to have BSD style ps
|
|
|
|
local pgid=$(ps -p $$ -o pgid | sed -e "/PGID/d")
|
|
|
|
children=$(ps -g $pgid -o pid | sed -e "/PID\|$$\|$pgid/d")
|
|
|
|
;;
|
|
|
|
*)
|
|
|
|
# everything else tries the GNU style
|
|
|
|
local pgid=$(ps -p $$ --no-headers -o "%r" | tr -d ' ')
|
|
|
|
children=$(pgrep -g $pgid | sed -e "/$$\|$pgid/d")
|
|
|
|
;;
|
|
|
|
esac
|
2012-10-30 15:55:20 +00:00
|
|
|
|
|
|
|
kill $children 2> /dev/null
|
|
|
|
wait $children 2> /dev/null
|
2012-05-09 20:36:28 +00:00
|
|
|
|
|
|
|
exit
|
|
|
|
}
|
|
|
|
|
2009-09-21 17:04:32 +00:00
|
|
|
print_stats() {
|
2011-12-02 21:32:03 +00:00
|
|
|
if [ "$ONLY_LIST" == 'y' ] ; then return ; fi
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
|
2012-10-30 15:55:20 +00:00
|
|
|
# Only count boards that completed
|
|
|
|
: $((TOTAL_CNT = `find ${skipp}* 2> /dev/null | wc -l`))
|
|
|
|
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
rm -f ${donep}* ${skipp}*
|
|
|
|
|
|
|
|
if [ $BUILD_MANY == 1 ] && [ -e "${OUTPUT_PREFIX}/ERR" ] ; then
|
2012-08-08 14:12:30 +00:00
|
|
|
ERR_LIST=`grep -riwl error ${OUTPUT_PREFIX}/ERR/`
|
2012-05-21 04:49:38 +00:00
|
|
|
ERR_LIST=`for f in $ERR_LIST ; do echo -n " $(basename $f)" ; done`
|
|
|
|
ERR_CNT=`echo $ERR_LIST | wc -w | awk '{print $1}'`
|
2012-08-08 14:12:30 +00:00
|
|
|
WRN_LIST=`grep -riwL error ${OUTPUT_PREFIX}/ERR/`
|
2012-05-21 04:49:38 +00:00
|
|
|
WRN_LIST=`for f in $WRN_LIST ; do echo -n " $(basename $f)" ; done`
|
|
|
|
WRN_CNT=`echo $WRN_LIST | wc -w | awk '{print $1}'`
|
2012-10-30 15:55:20 +00:00
|
|
|
else
|
|
|
|
# Remove the logs for any board that was interrupted
|
|
|
|
rm -f ${LOG_DIR}/${CUR_TGT}.MAKELOG ${LOG_DIR}/${CUR_TGT}.ERR
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
fi
|
|
|
|
|
2012-10-30 15:55:21 +00:00
|
|
|
: $((TOTAL_CNT -= ${SKIP_CNT}))
|
2009-09-21 17:04:32 +00:00
|
|
|
echo ""
|
|
|
|
echo "--------------------- SUMMARY ----------------------------"
|
2012-10-30 15:55:21 +00:00
|
|
|
if [ "$CONTINUE" = 'y' -o "$REBUILD_ERRORS" = 'y' ] ; then
|
|
|
|
echo "Boards skipped: ${SKIP_CNT}"
|
|
|
|
fi
|
2009-09-21 17:04:32 +00:00
|
|
|
echo "Boards compiled: ${TOTAL_CNT}"
|
|
|
|
if [ ${ERR_CNT} -gt 0 ] ; then
|
2012-05-21 04:49:38 +00:00
|
|
|
echo "Boards with errors: ${ERR_CNT} (${ERR_LIST} )"
|
|
|
|
fi
|
|
|
|
if [ ${WRN_CNT} -gt 0 ] ; then
|
|
|
|
echo "Boards with warnings but no errors: ${WRN_CNT} (${WRN_LIST} )"
|
2009-09-21 17:04:32 +00:00
|
|
|
fi
|
|
|
|
echo "----------------------------------------------------------"
|
2009-12-07 05:58:28 +00:00
|
|
|
|
2012-05-09 20:36:28 +00:00
|
|
|
if [ $BUILD_MANY == 1 ] ; then
|
2012-10-30 15:55:20 +00:00
|
|
|
kill_children
|
2012-05-09 20:36:28 +00:00
|
|
|
fi
|
|
|
|
|
2009-12-07 05:58:28 +00:00
|
|
|
exit $RC
|
2009-09-21 17:04:32 +00:00
|
|
|
}
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2009-09-21 17:04:32 +00:00
|
|
|
#-----------------------------------------------------------------------
|
2010-08-19 17:05:06 +00:00
|
|
|
|
2010-10-17 10:26:48 +00:00
|
|
|
# Build target groups selected by options, plus any command line args
|
|
|
|
set -- ${SELECTED} "$@"
|
|
|
|
# run PowerPC by default
|
2010-08-19 17:05:06 +00:00
|
|
|
[ $# = 0 ] && set -- powerpc
|
|
|
|
build_targets "$@"
|
Allow for parallel builds and saved output
The MAKEALL script cleverly runs make with the appropriate options
to use all of the cores on the system, but your average U-Boot build
can't make much use of more than a few cores. If you happen to have
a many-core server, your builds will leave most of the system idle.
In order to make full use of such a system, we need to build multiple
targets in parallel, and this requires directing make output into
multiple directories. We add a BUILD_NBUILDS variable, which allows
users to specify how many builds to run in parallel.
When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
default BUILD_DIR when BUILD_NBUILDS is greater than 1.
MAKEALL now tracks which builds are still running, and when one
finishes, it starts a new build.
Once each build finishes, we run "make tidy" on its directory, to reduce
the footprint.
As a result, we are left with a build directory with all of the built
targets still there for use, which means anyone who wanted to use
MAKEALL as part of a test harness can now do so.
Signed-off-by: Andy Fleming <afleming@freescale.com>
2012-04-24 19:33:51 +00:00
|
|
|
wait
|