Fix archive_build.sh to work with new build using board subdirs.

src/scripts/common.sh

-# Copyright (c) 2009 The Chromium OS Authors. All rights reserved.
+# Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Common constants for build scripts
 # This must evaluate properly for both /bin/bash and /bin/sh
 
 # All scripts should die on error unless commands are specifically excepted
 # by prefixing with '!' or surrounded by 'set +e' / 'set -e'.
 # TODO: Re-enable this once shflags is less prone to dying.
 #set -e
@@ skipping 78 matching lines @@
 DEFAULT_IMG_MIRROR=${CHROMEOS_IMG_MIRROR:-"${DEFAULT_CHROMEOS_SERVER}/ubuntu"}
 DEFAULT_IMG_SUITE=${CHROMEOS_IMG_SUITE:-"karmic"}
 
 # Default location for chroot
 DEFAULT_CHROOT_DIR=${CHROMEOS_CHROOT_DIR:-"$GCLIENT_ROOT/chroot"}
 
 # All output files from build should go under $DEFAULT_BUILD_ROOT, so that
 # they don't pollute the source directory.
 DEFAULT_BUILD_ROOT=${CHROMEOS_BUILD_ROOT:-"$SRC_ROOT/build"}
 
+# Set up a global ALL_BOARDS value
+ALL_BOARDS=$(cd ../overlays;ls -1d overlay-* 2>&-|sed 's,overlay-,,g')
+# Strip CR
+ALL_BOARDS=$(echo $ALL_BOARDS)
+# Set a default BOARD
+#DEFAULT_BOARD=x86-generic # or...
+DEFAULT_BOARD=$(echo $ALL_BOARDS | awk '{print $NF}')
+
 # Detect whether we're inside a chroot or not
 if [ -e /etc/debian_chroot ]
 then
   INSIDE_CHROOT=1
 else
   INSIDE_CHROOT=0
 fi
 
 # Directory locations inside the dev chroot
 CHROOT_TRUNK_DIR="/home/$USER/trunk"
@@ skipping 118 matching lines @@
 V_RED="\e[31m"
 V_YELLOW="\e[33m"
 
 function warn {
   echo -e "${V_YELLOW}Warning..: $1${V_VIDOFF}"
 }
 
 function error {
   echo -e "${V_RED}Error....: $1${V_VIDOFF}"
 }