# HG changeset patch
# User "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
# Date 1276454582 -7200
# Node ID 7130357d712b95133f3b76af957e0a887dabd0b8
# Parent  4a3ef29eadcdee65e72bbf1d88831251ae07221d
cc/gcc: store core build rules in an array

Using an array makes it easier to add new rules.
Besides, it is easy to expand from build rules to install rules

diff -r 4a3ef29eadcd -r 7130357d712b scripts/build/cc/gcc.sh
--- a/scripts/build/cc/gcc.sh	Sun Jun 13 20:31:42 2010 +0200
+++ b/scripts/build/cc/gcc.sh	Sun Jun 13 20:43:02 2010 +0200
@@ -92,6 +92,7 @@
     local tmp
     local -a extra_config
     local core_LDFLAGS
+    local -a core_targets
 
     while [ $# -ne 0 ]; do
         eval "${1}"
@@ -233,12 +234,10 @@
 
         if [ "${CT_CC_GCC_4_3_or_later}" = "y" ]; then
             libgcc_rule="libgcc.mvars"
-            build_rules="all-gcc all-target-libgcc"
-            install_rules="install-gcc install-target-libgcc"
+            core_targets=( gcc target-libgcc )
         else
             libgcc_rule="libgcc.mk"
-            build_rules="all-gcc"
-            install_rules="install-gcc"
+            core_targets=( gcc )
         fi
 
         # On bare metal and canadian build the host-compiler is used when
@@ -256,15 +255,14 @@
                               ${repair_cc}
         sed -r -i -e 's@-lc@@g' gcc/${libgcc_rule}
     else # build_libgcc
-            build_rules="all-gcc"
-            install_rules="install-gcc"
+        core_targets=( gcc )
     fi   # ! build libgcc
 
     CT_DoLog EXTRA "Building ${mode} core C compiler"
-    CT_DoExecLog ALL make ${PARALLELMFLAGS} ${build_rules}
+    CT_DoExecLog ALL make ${PARALLELMFLAGS} "${core_targets[@]/#/all-}"
 
     CT_DoLog EXTRA "Installing ${mode} core C compiler"
-    CT_DoExecLog ALL make ${install_rules}
+    CT_DoExecLog ALL make "${core_targets[@]/#/install-}"
 
     # Create a symlink ${CT_TARGET}-cc to ${CT_TARGET}-gcc to always be able
     # to call the C compiler with the same, somewhat canonical name.