ROOTDIR=$PWD
LOGFILE=$ROOTDIR/linux_install.log
ERRORFILE=$ROOTDIR/linux_install.err
-GCC4ARM_VERSION=gcc-arm-none-eabi-4_6-2012q1
-GCC4ARM_FILENAME=gcc-arm-none-eabi-4_6-2012q1-20120316.tar.bz2
-GCC4ARM_URL=https://launchpad.net/gcc-arm-embedded/4.6/4.6-2012-q1-update/+download/$GCC4ARM_FILENAME
+GCC4ARM_VERSION=gcc-arm-none-eabi-4_8-2014q1
+GCC4ARM_FILENAME=gcc-arm-none-eabi-4_8-2014q1-20140314-linux.tar.bz2
+GCC4ARM_URL=https://launchpad.net/gcc-arm-embedded/4.8/4.8-2014-q1-update/+download/$GCC4ARM_FILENAME
GCC4ARM_TAR=$ROOTDIR/$GCC4ARM_FILENAME
-GCC4ARM_MD5=3999e0ce25ecd97b3138f3b0dc13c76f
+GCC4ARM_MD5=72b0d06ae16b303c25fd70b2883d3950
GCC4ARM_EXTRACT=$ROOTDIR/$GCC4ARM_VERSION
GCC4ARM_DIR=$ROOTDIR/gcc-arm-none-eabi
GCC4ARM_BINDIR=$GCC4ARM_DIR/bin
-GCC4ARM_LIBEXEC=$GCC4ARM_DIR/libexec/gcc/arm-none-eabi/4.6.2
-NEWBIN_URL=https://github.com/adamgreen/GCC-ARM-Embedded-20120316/tarball/master
-NEWBIN_TAR=$ROOTDIR/GCC-ARM-Embedded-20120316.tar.gz
-NEWBIN_MD5=ab3e32a3418a38121eceb267e4366848
-NEWBIN_BASEDIR=$ROOTDIR/GCC-ARM-Embedded
-NEWBIN_DIR=$NEWBIN_BASEDIR/lin32
-OUR_MAKE=make
BUILDSHELL_CMD=$ROOTDIR/BuildShell
-BUILDSHELL_DEBUG_CMD=$ROOTDIR/BuildShellDebug
echo Logging install results to $LOGFILE
exit 1
fi
-echo Downloading updated GCC binaries from github...
-rm $NEWBIN_TAR >/dev/null 2>/dev/null
-echo `date` Executing wget -O $NEWBIN_TAR $NEWBIN_URL>>$LOGFILE
-wget -O $NEWBIN_TAR $NEWBIN_URL
-
-echo Validating md5 signature of updated GCC binaries...
-echo `date` Validating md5 signature of csgcc4mac project>>$LOGFILE
-archive_match=`md5sum $NEWBIN_TAR | grep -c $NEWBIN_MD5`
-if [ "$archive_match" != "1" ] ; then
- echo $NEWBIN_TAR failed MD5 signature check.>>$LOGFILE
- echo `date` Failure forced early exit>>$LOGFILE
- cat $LOGFILE
- rm -f $ERRORFILE
- popd >/dev/null
- read -n 1 -sp "Press any key to continue..." dummy ; echo
- exit 1
-fi
-
echo Extracting GNU Tools for ARM Embedded Processors...
rm -r $GCC4ARM_DIR >/dev/null 2>/dev/null
RunAndLog tar xf $GCC4ARM_TAR
RunAndLog mv $GCC4ARM_EXTRACT $GCC4ARM_DIR
-echo Extracting updated GCC binaries...
-RunAndLog tar -x --xform s/adamgreen-GCC-ARM-Embedded-[0-9]*-[a-f0-9]*/GCC-ARM-Embedded/ -f $NEWBIN_TAR
-
-echo Installing updated GCC binaries...
-RunAndLog cp $NEWBIN_DIR/arm-none-eabi-gdb $GCC4ARM_BINDIR/
-
echo Creating helper scripts...
echo "#! /usr/bin/env bash">$BUILDSHELL_CMD
echo "# Modify next line and set destination drive to match mbed device">>$BUILDSHELL_CMD
echo "exec bash">>$BUILDSHELL_CMD
chmod +x $BUILDSHELL_CMD
-echo "#! /usr/bin/env bash">$BUILDSHELL_DEBUG_CMD
-echo "# Modify next line and set destination drive to match mbed device">>$BUILDSHELL_DEBUG_CMD
-echo "export LPC_DEPLOY='cp PROJECT.bin /media/MBED/ ; sync'">>$BUILDSHELL_DEBUG_CMD
-echo>>$BUILDSHELL_DEBUG_CMD
-echo "SCRIPT_PATH=\$0">>$BUILDSHELL_DEBUG_CMD
-echo "SCRIPT_PATH=\${SCRIPT_PATH%/*}">>$BUILDSHELL_DEBUG_CMD
-echo "cd \$SCRIPT_PATH">>$BUILDSHELL_DEBUG_CMD
-echo "SCRIPT_PATH=\$PWD">>$BUILDSHELL_DEBUG_CMD
-echo "export PATH=\$SCRIPT_PATH/gcc-arm-none-eabi/bin:\$PATH">>$BUILDSHELL_DEBUG_CMD
-echo "export GCC4MBED_TYPE=Debug">>$BUILDSHELL_DEBUG_CMD
-echo "exec bash">>$BUILDSHELL_DEBUG_CMD
-chmod +x $BUILDSHELL_DEBUG_CMD
-
-# Place arm-none-eabi-* tools in the path before building gcc4mbed code.
-PATH=$GCC4ARM_BINDIR:$PATH
-
-echo Performing a clean build of the gcc4mbed samples...
-RunAndLog $OUR_MAKE clean
-RunAndLog $OUR_MAKE
-
echo Cleaning up intermediate files...
-RunAndLog rm -r $NEWBIN_BASEDIR
-RunAndLog rm $NEWBIN_TAR
RunAndLog rm $GCC4ARM_TAR
echo
-echo To build gcc4mbed samples, you will first need to run the following script
+echo To build Smoothie, you will first need to run the following script
echo so that your environment variables are set correctly:
echo $BUILDSHELL_CMD
echo You will want to run this each time you start a new Terminal. You
echo can simply double-click on this script file from Finder to launch a
-echo bash Terminal that has been properly initialized for building gcc4mbed
-echo based code. Feel free to customize it as you desire.
+echo bash Terminal that has been properly initialized for building. Feel
+echo free to customize it as you desire.
echo
echo You can also just edit your existing setup script such as \~/.profile
echo to update the PATH environment variable to include: