poky/poky-init-build-env
Otavio Salvador 740ea68258 poky-init-build-env: unset BBPATH
When using OpenEmbedded and Yocto I had it previously set to OE and
this made bitbake to get confused. This was difficult to figure out
and then it seems safer and cleaner if the script unset it to avoid
this confusing behaviour.

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-18 00:20:21 +00:00

1.5 KiB
Executable File

#!/bin/sh

Poky Build Enviroment Setup Script

Copyright (C) 2006-2007 OpenedHand Ltd.

This program is free software; you can redistribute it and/or modify

it under the terms of the GNU General Public License as published by

the Free Software Foundation; either version 2 of the License, or

(at your option) any later version.

This program is distributed in the hope that it will be useful,

but WITHOUT ANY WARRANTY; without even the implied warranty of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

GNU General Public License for more details.

You should have received a copy of the GNU General Public License

along with this program; if not, write to the Free Software

Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Normally this is called as '. ./poky-init-buildenv builddir'

This works in most shells (not dash), but not all of them pass arg1 when

being sourced. To workaround the shell limitation use "set arg1" prior

to sourcing this script.

if [ "x$0" = "x./poky-init-build-env" ]; then echo "Error: This script needs to be sourced. Please run as '. ./poky-init-build-env'" else if [ -n "$BASH_SOURCE" ]; then OEROOT="dirname $BASH_SOURCE" else OEROOT="pwd" fi OEROOT=readlink -f "$OEROOT" export OEROOT . $OEROOT/scripts/poky-env-internal $OEROOT/scripts/poky-setup-builddir unset OEROOT unset BBPATH [ -n "$BUILDDIR" ] && cd $BUILDDIR fi