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.
|
|
|
|
|
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
|
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
|
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: "")
|
|
|
|
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}
|
|
|
|
}
|
|
|
|
|
2012-03-05 15:10:51 +00:00
|
|
|
SHORT_OPTS="ha:c:v:s:lmM"
|
|
|
|
LONG_OPTS="help,arch:,cpu:,vendor:,soc:,list,maintainers,mails"
|
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=''
|
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
|
|
|
|
opt_c="${opt_c%)} || \$3 == \"$2\")"
|
|
|
|
else
|
|
|
|
opt_c="(\$3 == \"$2\")"
|
|
|
|
fi
|
|
|
|
SELECTED='y'
|
|
|
|
shift 2 ;;
|
|
|
|
-s|--soc)
|
|
|
|
# echo "Option SoC: argument \`$2'"
|
|
|
|
if [ "$opt_s" ] ; then
|
|
|
|
opt_s="${opt_s%)} || \$6 == \"$2\")"
|
|
|
|
else
|
|
|
|
opt_s="(\$6 == \"$2\")"
|
|
|
|
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 ;;
|
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
|
|
|
|
# echo "Remaining arguments:"
|
|
|
|
# for arg do echo '--> '"\`$arg'" ; done
|
|
|
|
|
|
|
|
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"
|
|
|
|
|
|
|
|
if [ "$SELECTED" ] ; then
|
|
|
|
SELECTED=$(awk '('"$FILTER"') { print $1 }' 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
|
|
|
|
|
2003-12-06 19:49:23 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
if [ "${CROSS_COMPILE}" ] ; then
|
|
|
|
MAKE="make CROSS_COMPILE=${CROSS_COMPILE}"
|
|
|
|
else
|
|
|
|
MAKE=make
|
|
|
|
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
|
|
|
|
find "${LOG_DIR}/" -type f -exec rm -f {} +
|
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
|
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
|
|
|
|
boards_by_field()
|
|
|
|
{
|
|
|
|
awk \
|
|
|
|
-v field="$1" \
|
|
|
|
-v select="$2" \
|
|
|
|
'($1 !~ /^#/ && $field == select) { print $1 }' \
|
|
|
|
boards.cfg
|
|
|
|
}
|
|
|
|
boards_by_arch() { boards_by_field 2 "$@" ; }
|
|
|
|
boards_by_cpu() { boards_by_field 3 "$@" ; }
|
2010-11-30 09:45:04 +00:00
|
|
|
boards_by_soc() { boards_by_field 6 "$@" ; }
|
2010-08-19 17:05:06 +00:00
|
|
|
|
2003-03-31 17:27:09 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC5xx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-08-19 17:05:06 +00:00
|
|
|
LIST_5xx="$(boards_by_cpu mpc5xx)"
|
2003-03-31 17:27:09 +00:00
|
|
|
|
2003-07-16 21:53:01 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC5xxx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_5xxx="$(boards_by_cpu mpc5xxx)"
|
2003-07-16 21:53:01 +00:00
|
|
|
|
2007-07-27 12:43:59 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC512x Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_512x="$(boards_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
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_8xx="$(boards_by_cpu mpc8xx)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
|
|
|
#########################################################################
|
|
|
|
## PPC4xx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_4xx="$(boards_by_cpu ppc4xx)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2004-10-28 00:09:35 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC8220 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-08-19 17:05:06 +00:00
|
|
|
LIST_8220="$(boards_by_cpu mpc8220)"
|
2004-10-28 00:09:35 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC824x Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_824x="$(boards_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
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_8260="$(boards_by_cpu mpc8260)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2005-07-28 15:08:46 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC83xx Systems (includes 8349, etc.)
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_83xx="$(boards_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.)
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_85xx="$(boards_by_cpu mpc85xx)"
|
2003-10-15 23:53:47 +00:00
|
|
|
|
2007-05-23 19:09:46 +00:00
|
|
|
#########################################################################
|
|
|
|
## MPC86xx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_86xx="$(boards_by_cpu mpc86xx)"
|
2007-05-23 19:09:46 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
## 74xx/7xx Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-06 07:05:45 +00:00
|
|
|
LIST_74xx_7xx="$(boards_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_8220} \
|
|
|
|
${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
|
|
|
|
#########################################################################
|
|
|
|
|
2010-08-19 17:05:06 +00:00
|
|
|
LIST_SA="$(boards_by_cpu sa1100)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
|
|
|
#########################################################################
|
|
|
|
## ARM9 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2011-09-08 05:01:24 +00:00
|
|
|
LIST_ARM9="$(boards_by_cpu arm920t) \
|
|
|
|
$(boards_by_cpu arm926ejs) \
|
|
|
|
$(boards_by_cpu arm925t) \
|
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
|
|
|
|
#########################################################################
|
2012-05-09 20:36:28 +00:00
|
|
|
LIST_ARM11="$(boards_by_cpu arm1136)"
|
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
|
|
|
|
|
|
|
LIST_ARMV7="$(boards_by_cpu armv7)"
|
2009-01-27 17:19:12 +00:00
|
|
|
|
2008-05-24 10:47:46 +00:00
|
|
|
#########################################################################
|
|
|
|
## AT91 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2011-08-04 11:08:50 +00:00
|
|
|
LIST_at91="$(boards_by_soc at91)"
|
2008-05-24 10:47:46 +00:00
|
|
|
|
2002-11-02 23:17:16 +00:00
|
|
|
#########################################################################
|
|
|
|
## Xscale Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-03 22:21:51 +00:00
|
|
|
LIST_pxa="$(boards_by_cpu pxa)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2012-04-25 09:36:13 +00:00
|
|
|
LIST_ixp="$(boards_by_cpu ixp)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2008-04-20 22:35:52 +00:00
|
|
|
#########################################################################
|
|
|
|
## ARM groups
|
|
|
|
#########################################################################
|
2003-10-14 19:43:55 +00:00
|
|
|
|
2009-01-27 17:19:12 +00:00
|
|
|
LIST_arm=" \
|
|
|
|
${LIST_SA} \
|
|
|
|
${LIST_ARM9} \
|
|
|
|
${LIST_ARM10} \
|
|
|
|
${LIST_ARM11} \
|
2010-06-18 04:50:01 +00:00
|
|
|
${LIST_ARMV7} \
|
2009-01-27 17:19:12 +00:00
|
|
|
${LIST_at91} \
|
|
|
|
${LIST_pxa} \
|
|
|
|
${LIST_ixp} \
|
2005-01-09 23:16:25 +00:00
|
|
|
"
|
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
|
|
|
#########################################################################
|
|
|
|
|
2007-08-10 20:34:48 +00:00
|
|
|
LIST_mips4kc=" \
|
|
|
|
incaip \
|
2008-01-16 17:27:51 +00:00
|
|
|
qemu_mips \
|
2009-01-21 16:25:01 +00:00
|
|
|
vct_platinum \
|
|
|
|
vct_platinum_small \
|
|
|
|
vct_platinum_onenand \
|
|
|
|
vct_platinum_onenand_small \
|
|
|
|
vct_platinumavc \
|
|
|
|
vct_platinumavc_small \
|
|
|
|
vct_platinumavc_onenand \
|
|
|
|
vct_platinumavc_onenand_small \
|
|
|
|
vct_premium \
|
|
|
|
vct_premium_small \
|
|
|
|
vct_premium_onenand \
|
|
|
|
vct_premium_onenand_small \
|
2007-08-10 20:34:48 +00:00
|
|
|
"
|
2003-03-27 12:09:35 +00:00
|
|
|
|
2007-08-10 20:34:48 +00:00
|
|
|
LIST_au1xx0=" \
|
|
|
|
dbau1000 \
|
|
|
|
dbau1100 \
|
|
|
|
dbau1500 \
|
|
|
|
dbau1550 \
|
|
|
|
gth2 \
|
|
|
|
"
|
2003-10-09 20:09:04 +00:00
|
|
|
|
2007-08-10 20:34:48 +00:00
|
|
|
LIST_mips=" \
|
|
|
|
${LIST_mips4kc} \
|
|
|
|
${LIST_mips5kc} \
|
|
|
|
${LIST_au1xx0} \
|
|
|
|
"
|
2003-03-27 12:09:35 +00:00
|
|
|
|
2005-08-13 22:27:00 +00:00
|
|
|
#########################################################################
|
|
|
|
## MIPS Systems (little endian)
|
|
|
|
#########################################################################
|
|
|
|
|
2011-11-24 03:57:56 +00:00
|
|
|
LIST_xburst_el=" \
|
2011-10-12 04:24:06 +00:00
|
|
|
qi_lb60 \
|
|
|
|
"
|
2005-08-13 22:27:00 +00:00
|
|
|
|
2007-08-10 20:34:48 +00:00
|
|
|
LIST_au1xx0_el=" \
|
|
|
|
dbau1550_el \
|
2007-10-27 06:00:25 +00:00
|
|
|
pb1000 \
|
2007-08-10 20:34:48 +00:00
|
|
|
"
|
|
|
|
LIST_mips_el=" \
|
2011-11-24 03:57:56 +00:00
|
|
|
${LIST_xburst_el} \
|
2007-08-10 20:34:48 +00:00
|
|
|
${LIST_au1xx0_el} \
|
|
|
|
"
|
2011-11-18 19:21:37 +00:00
|
|
|
#########################################################################
|
|
|
|
## OpenRISC Systems
|
|
|
|
#########################################################################
|
|
|
|
|
|
|
|
LIST_openrisc="$(boards_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
|
|
|
#########################################################################
|
|
|
|
|
2011-04-13 09:43:28 +00:00
|
|
|
LIST_x86="$(boards_by_arch x86)"
|
2003-05-31 18:35:21 +00:00
|
|
|
|
2004-10-10 21:27:30 +00:00
|
|
|
#########################################################################
|
|
|
|
## Nios-II Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2011-06-27 03:00:19 +00:00
|
|
|
LIST_nios2="$(boards_by_arch nios2)"
|
2004-10-10 21:27:30 +00:00
|
|
|
|
2004-07-10 23:48:41 +00:00
|
|
|
#########################################################################
|
|
|
|
## MicroBlaze Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-08-19 17:05:06 +00:00
|
|
|
LIST_microblaze="$(boards_by_arch microblaze)"
|
2004-07-10 23:48:41 +00:00
|
|
|
|
2006-01-26 22:38:46 +00:00
|
|
|
#########################################################################
|
|
|
|
## ColdFire Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2011-09-25 19:27:19 +00:00
|
|
|
LIST_m68k="$(boards_by_arch m68k)
|
2007-08-10 20:34:48 +00:00
|
|
|
EB+MCF-EV123 \
|
|
|
|
EB+MCF-EV123_internal \
|
2008-01-14 23:43:33 +00:00
|
|
|
M52277EVB \
|
2007-08-17 00:23:50 +00:00
|
|
|
M5235EVB \
|
2008-08-11 13:41:49 +00:00
|
|
|
M54451EVB \
|
2007-08-16 20:05:11 +00:00
|
|
|
M54455EVB \
|
2006-04-20 06:42:42 +00:00
|
|
|
"
|
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
|
|
|
|
#########################################################################
|
|
|
|
|
2010-08-19 17:05:06 +00:00
|
|
|
LIST_avr32="$(boards_by_arch avr32)"
|
2006-10-24 12:42:37 +00:00
|
|
|
|
2007-03-09 05:40:56 +00:00
|
|
|
#########################################################################
|
|
|
|
## Blackfin Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-19 06:41:26 +00:00
|
|
|
LIST_blackfin="$(boards_by_arch blackfin)"
|
2007-03-09 05:40:56 +00:00
|
|
|
|
2007-11-27 08:44:53 +00:00
|
|
|
#########################################################################
|
|
|
|
## SH Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-10-19 16:22:25 +00:00
|
|
|
LIST_sh2="$(boards_by_cpu sh2)"
|
2010-10-19 16:28:29 +00:00
|
|
|
LIST_sh3="$(boards_by_cpu sh3)"
|
2010-10-19 16:35:28 +00:00
|
|
|
LIST_sh4="$(boards_by_cpu sh4)"
|
2008-04-20 22:35:52 +00:00
|
|
|
|
2010-10-19 16:35:28 +00:00
|
|
|
LIST_sh="$(boards_by_arch sh)"
|
2007-11-27 08:44:53 +00:00
|
|
|
|
2008-03-28 08:47:00 +00:00
|
|
|
#########################################################################
|
|
|
|
## SPARC Systems
|
|
|
|
#########################################################################
|
|
|
|
|
2010-08-19 17:05:06 +00:00
|
|
|
LIST_sparc="$(boards_by_arch sparc)"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
2011-10-19 20:41:10 +00:00
|
|
|
#########################################################################
|
|
|
|
## NDS32 Systems
|
|
|
|
#########################################################################
|
|
|
|
|
|
|
|
LIST_nds32="$(boards_by_arch nds32)"
|
|
|
|
|
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
|
|
|
|
local line=`egrep -i "^[[:space:]]*${target}[[:space:]]" boards.cfg`
|
|
|
|
|
|
|
|
if [ -z "${line}" ] ; then echo "" ; return ; fi
|
|
|
|
|
|
|
|
set ${line}
|
|
|
|
|
|
|
|
# add default board name if needed
|
|
|
|
[ $# = 3 ] && set ${line} ${1}
|
|
|
|
|
|
|
|
CONFIG_NAME="${1%_config}"
|
|
|
|
|
|
|
|
[ "${BOARD_NAME}" ] || BOARD_NAME="${1%_config}"
|
|
|
|
|
|
|
|
if [ "$4" = "-" ] ; then
|
|
|
|
board=${BOARD_NAME}
|
|
|
|
else
|
|
|
|
board="$4"
|
|
|
|
fi
|
|
|
|
|
|
|
|
[ $# -gt 4 ] && [ "$5" != "-" ] && vendor="$5"
|
|
|
|
[ $# -gt 6 ] && [ "$7" != "-" ] && {
|
|
|
|
tmp="${7%:*}"
|
|
|
|
if [ "$tmp" ] ; then
|
|
|
|
CONFIG_NAME="$tmp"
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
|
|
|
# Assign board directory to BOARDIR variable
|
|
|
|
if [ -z "${vendor}" ] ; then
|
|
|
|
BOARDDIR=${board}
|
|
|
|
else
|
|
|
|
BOARDDIR=${vendor}/${board}
|
|
|
|
fi
|
|
|
|
|
|
|
|
echo "${CONFIG_NAME}:${BOARDDIR}"
|
|
|
|
}
|
|
|
|
|
|
|
|
get_target_maintainers() {
|
|
|
|
local name=`echo $1 | cut -d : -f 1`
|
|
|
|
|
|
|
|
if ! grep -qsi "[[:blank:]]${name}[[:blank:]]" MAINTAINERS ; then
|
|
|
|
echo ""
|
|
|
|
return ;
|
|
|
|
fi
|
|
|
|
|
|
|
|
local line=`tac MAINTAINERS | grep -ni "[[:blank:]]${name}[[:blank:]]" | cut -d : -f 1`
|
|
|
|
local mail=`tac MAINTAINERS | tail -n +${line} | \
|
|
|
|
sed -n ":start /.*@.*/ { b mail } ; n ; b start ; :mail /.*@.*/ { p ; n ; b mail } ; q" | \
|
|
|
|
sed "s/^.*<//;s/>.*$//"`
|
|
|
|
echo "$mail"
|
|
|
|
}
|
|
|
|
|
|
|
|
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_"
|
|
|
|
|
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}"
|
|
|
|
else
|
|
|
|
output_dir="${OUTPUT_PREFIX}"
|
|
|
|
fi
|
|
|
|
|
|
|
|
export BUILD_DIR="${output_dir}"
|
2002-11-02 23:17:16 +00:00
|
|
|
|
|
|
|
${MAKE} distclean >/dev/null
|
2010-09-14 19:48:16 +00:00
|
|
|
${MAKE} -s ${target}_config
|
2006-09-01 17:49:50 +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
|
|
|
${MAKE} ${JOBS} all \
|
|
|
|
>${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
|
|
|
|
${MAKE} tidy
|
|
|
|
|
|
|
|
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-05-21 04:49:37 +00:00
|
|
|
if [ $BUILD_MANY == 1 ] ; then
|
|
|
|
build_target ${t} ${TOTAL_CNT} &
|
|
|
|
else
|
|
|
|
build_target ${t} ${TOTAL_CNT}
|
|
|
|
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() {
|
|
|
|
kill -- "-$1"
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
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}'`
|
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
|
|
|
|
|
2009-09-21 17:04:32 +00:00
|
|
|
echo ""
|
|
|
|
echo "--------------------- SUMMARY ----------------------------"
|
|
|
|
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
|
|
|
|
kill_children $$ &
|
|
|
|
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
|