In that case, we need to modify the “function”, do we?
Robbert _____ From: [email protected] [mailto:[email protected]] On Behalf Of Andrey Filippov Sent: Tuesday, December 01, 2009 4:07 PM To: Robbert Cc: [email protected] Subject: Re: Source init_env in current working directory Robbert, init_env is not part of the project - it is generated by make init_env And the top Makefile is also generated (most code is in "functions") Andrey On Mon, Nov 30, 2009 at 9:25 PM, Robbert <[email protected]> wrote: Hi Andrey, When you go straight to your working directory and source the init_env there (eg. “source ../../../init_env” OR “source symbol_link_file_of_init_env” ), the script doesn’t work properly. I modified the file to make it work better, hope it will help. Robbert =========================================== filename=`readlink -f ${BASH_SOURCE[0]}` export AXIS_TOP_DIR=`dirname $filename` echo "Prepending \"$AXIS_TOP_DIR/tools/build/bin\" to PATH." export PATH="$AXIS_TOP_DIR/tools/build/bin:$PATH" echo "Prepending \"/usr/local/cris/bin\" to PATH." export PATH="/usr/local/cris/bin:$PATH" export AXIS_KERNEL_DIR="$AXIS_TOP_DIR/os/linux-2.6" No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.87/2535 - Release Date: 11/30/09 21:05:00
_______________________________________________ Support-list mailing list [email protected] http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
