[Elphel-support] Source init_env in current working directory

[Andrey Filippov]

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 <rma at vmsys.com> 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"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20091130/82a720cc/attachment-0002.html>