2006-11-23 12:15:17 +00:00
#!/bin/sh
2012-03-25 11:46:15 +00:00
# OE-Core Build Environment Setup Script
2006-11-23 12:15:17 +00:00
#
2011-04-21 11:26:25 +00:00
# Copyright (C) 2006-2011 Linux Foundation
2006-11-23 12:15:17 +00:00
#
# 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
2010-11-24 22:25:28 +00:00
# It is assumed OEROOT is already defined when this is called
if [ -z "$OEROOT" ]; then
echo >&2 "Error: OEROOT is not defined!"
oe-init-build-env, scripts/oe-buildenv-internal: add error detecting for $BDIR
[YOCTO #671]
"readlink -f" in Ubuntu 10.04 is buggy: it doesn't ignore a trailing / (e.g.,
"readlink -f /tmp/non-existent-dir/" returns nothing, but according to
http://www.gnu.org/s/coreutils/manual/coreutils.pdf it should do that --
hence we get bug 671. It seems Ubuntu 10.10 or even later Ubuntu 11.04,
and other Linux distributions(e.g., Open Suse 11.4) haven't such an issue.
So I think we should detect this and ask Ubuntu 10.04 users to avoid supply
a path with trailing slash here.
Moreever, I also add the detection of non-existent path, e.g.,
source oe-init-build-env /non-existent-dir/build
can be detected and we'll print an error msg.
And, if we get errors in oe-buildenv-internal, we should stop the script
and shouldn't further run.
(From OE-Core rev: 651ccb3b031d9ccb8331505a51171372002230d9)
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-02 06:08:32 +00:00
return 1
2010-11-24 22:25:28 +00:00
fi
2007-05-16 13:48:29 +00:00
2016-03-15 16:58:07 +00:00
if [ -z "$OE_SKIP_SDK_CHECK" ] && [ -n "$OECORE_SDK_VERSION" ]; then
2012-10-02 13:08:13 +00:00
echo >&2 "Error: The OE SDK/ADT was detected as already being present in this shell environment. Please use a clean shell when sourcing this environment script."
return 1
fi
2016-06-01 12:17:23 +00:00
# Make sure we're not using python v3.x as 'python', we don't support it.
py_v2_check=$(/usr/bin/env python --version 2>&1 | grep "Python 3")
if [ -n "$py_v2_check" ]; then
echo >&2 "OpenEmbedded requires 'python' to be python v2 (>= 2.7.3), not python v3."
echo >&2 "Please set up python v2 as your default 'python' interpreter."
2016-03-15 16:58:07 +00:00
return 1
2013-06-07 17:16:41 +00:00
fi
2016-06-01 12:17:23 +00:00
unset py_v2_check
2013-06-07 17:16:41 +00:00
2016-06-01 12:17:23 +00:00
py_v27_check=$(python -c 'import sys; print sys.version_info >= (2,7,3)')
if [ "$py_v27_check" != "True" ]; then
echo >&2 "OpenEmbedded requires 'python' to be python v2 (>= 2.7.3), not python v3."
echo >&2 "Please upgrade your python v2."
fi
unset py_v27_check
# We potentially have code that doesn't parse correctly with older versions
# of Python, and rather than fixing that and being eternally vigilant for
# any other new feature use, just check the version here.
py_v34_check=$(python3 -c 'import sys; print(sys.version_info >= (3,4,0))')
if [ "$py_v34_check" != "True" ]; then
echo >&2 "BitBake requires Python 3.4.0 or later as 'python3'"
2016-03-15 16:58:07 +00:00
return 1
2013-06-07 17:16:41 +00:00
fi
2016-06-01 12:17:23 +00:00
unset py_v34_check
2013-06-07 17:16:41 +00:00
2016-03-15 16:58:07 +00:00
if [ -z "$BDIR" ]; then
if [ -z "$1" ]; then
2010-07-21 13:55:39 +00:00
BDIR="build"
2010-11-28 13:11:57 +00:00
else
2011-08-04 06:53:20 +00:00
BDIR="$1"
if [ "$BDIR" = "/" ]; then
echo >&2 "Error: / is not supported as a build directory."
return 1
fi
# Remove any possible trailing slashes. This is used to work around
# buggy readlink in Ubuntu 10.04 that doesn't ignore trailing slashes
# and hence "readlink -f new_dir_to_be_created/" returns empty.
2016-03-15 16:58:07 +00:00
BDIR=$(echo $BDIR | sed -re 's|/+$||')
2011-08-04 06:53:20 +00:00
2016-03-15 16:58:07 +00:00
BDIR=$(readlink -f "$BDIR")
2011-08-04 06:53:20 +00:00
if [ -z "$BDIR" ]; then
2016-03-15 16:58:07 +00:00
PARENTDIR=$(dirname "$1")
2011-08-04 06:53:20 +00:00
echo >&2 "Error: the directory $PARENTDIR does not exist?"
oe-init-build-env, scripts/oe-buildenv-internal: add error detecting for $BDIR
[YOCTO #671]
"readlink -f" in Ubuntu 10.04 is buggy: it doesn't ignore a trailing / (e.g.,
"readlink -f /tmp/non-existent-dir/" returns nothing, but according to
http://www.gnu.org/s/coreutils/manual/coreutils.pdf it should do that --
hence we get bug 671. It seems Ubuntu 10.10 or even later Ubuntu 11.04,
and other Linux distributions(e.g., Open Suse 11.4) haven't such an issue.
So I think we should detect this and ask Ubuntu 10.04 users to avoid supply
a path with trailing slash here.
Moreever, I also add the detection of non-existent path, e.g.,
source oe-init-build-env /non-existent-dir/build
can be detected and we'll print an error msg.
And, if we get errors in oe-buildenv-internal, we should stop the script
and shouldn't further run.
(From OE-Core rev: 651ccb3b031d9ccb8331505a51171372002230d9)
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-02 06:08:32 +00:00
return 1
fi
2010-11-28 13:11:57 +00:00
fi
2016-03-15 16:58:07 +00:00
if [ -n "$2" ]; then
2012-05-12 07:41:44 +00:00
BITBAKEDIR="$2"
fi
2010-07-21 13:55:39 +00:00
fi
2016-03-15 16:58:07 +00:00
if [ "${BDIR#/}" != "$BDIR" ]; then
2010-07-21 13:55:39 +00:00
BUILDDIR="$BDIR"
else
2016-03-15 16:58:07 +00:00
BUILDDIR="$(pwd)/$BDIR"
2007-07-17 13:29:36 +00:00
fi
2008-10-28 10:01:03 +00:00
unset BDIR
2010-07-21 13:55:39 +00:00
2016-03-15 16:58:07 +00:00
if [ -z "$BITBAKEDIR" ]; then
BITBAKEDIR="$OEROOT/bitbake$BBEXTRA"
2012-05-09 16:44:23 +00:00
fi
2008-10-28 10:01:03 +00:00
2016-03-15 16:58:07 +00:00
BITBAKEDIR=$(readlink -f "$BITBAKEDIR")
BUILDDIR=$(readlink -f "$BUILDDIR")
2006-11-23 12:15:17 +00:00
2016-03-15 16:58:07 +00:00
if [ ! -d "$BITBAKEDIR" ]; then
2011-05-18 11:33:27 +00:00
echo >&2 "Error: The bitbake directory ($BITBAKEDIR) does not exist! Please ensure a copy of bitbake exists at this location"
oe-init-build-env, scripts/oe-buildenv-internal: add error detecting for $BDIR
[YOCTO #671]
"readlink -f" in Ubuntu 10.04 is buggy: it doesn't ignore a trailing / (e.g.,
"readlink -f /tmp/non-existent-dir/" returns nothing, but according to
http://www.gnu.org/s/coreutils/manual/coreutils.pdf it should do that --
hence we get bug 671. It seems Ubuntu 10.10 or even later Ubuntu 11.04,
and other Linux distributions(e.g., Open Suse 11.4) haven't such an issue.
So I think we should detect this and ask Ubuntu 10.04 users to avoid supply
a path with trailing slash here.
Moreever, I also add the detection of non-existent path, e.g.,
source oe-init-build-env /non-existent-dir/build
can be detected and we'll print an error msg.
And, if we get errors in oe-buildenv-internal, we should stop the script
and shouldn't further run.
(From OE-Core rev: 651ccb3b031d9ccb8331505a51171372002230d9)
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-02 06:08:32 +00:00
return 1
2006-11-23 12:15:17 +00:00
fi
2013-04-09 10:24:13 +00:00
# Make sure our paths are at the beginning of $PATH
2016-03-15 16:48:53 +00:00
for newpath in "$BITBAKEDIR/bin" "$OEROOT/scripts"; do
# Remove any existences of $newpath from $PATH
2016-03-21 11:41:46 +00:00
PATH=$(echo $PATH | sed -re "s#(^|:)$newpath(:|$)#\2#g;s#^:##")
2016-03-15 16:48:53 +00:00
# Add $newpath to $PATH
PATH="$newpath:$PATH"
done
unset BITBAKEDIR newpath
2010-05-12 14:43:51 +00:00
2011-04-20 15:44:10 +00:00
# Used by the runqemu script
2010-11-28 12:41:09 +00:00
export BUILDDIR
2010-11-28 13:11:57 +00:00
export PATH
2015-12-03 23:09:56 +00:00
2016-03-24 17:49:22 +00:00
BB_ENV_EXTRAWHITE_OE="MACHINE DISTRO TCMODE TCLIBC HTTP_PROXY http_proxy \
2013-01-29 13:16:28 +00:00
HTTPS_PROXY https_proxy FTP_PROXY ftp_proxy FTPS_PROXY ftps_proxy ALL_PROXY \
all_proxy NO_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY \
SDKMACHINE BB_NUMBER_THREADS BB_NO_NETWORK PARALLEL_MAKE GIT_PROXY_COMMAND \
2016-06-23 12:07:01 +00:00
SOCKS5_PASSWD SOCKS5_USER SCREENDIR STAMPS_DIR BBPATH_EXTRA BB_SETSCENE_ENFORCE"
2015-12-03 23:09:56 +00:00
2016-04-04 19:16:19 +00:00
BB_ENV_EXTRAWHITE="$(echo $BB_ENV_EXTRAWHITE $BB_ENV_EXTRAWHITE_OE | tr ' ' '\n' | LC_ALL=C sort --unique | tr '\n' ' ')"
2016-03-24 17:49:22 +00:00
2016-03-15 16:53:31 +00:00
export BB_ENV_EXTRAWHITE