From: Andreas Oberritter <obi@opendreambox.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] scripts/bitbake: allow switching between build directories
Date: Tue, 27 Mar 2012 15:09:11 +0200 [thread overview]
Message-ID: <4F71BBF7.4030001@opendreambox.org> (raw)
In-Reply-To: <0b6dadd78b527731df18b8fa308d714b6d3ef956.1332848153.git.paul.eggleton@linux.intel.com>
On 27.03.2012 13:50, Paul Eggleton wrote:
> The recent addition of the check to ensure the user was in their build
> directory disabled the ability to switch between build directories
> without re-running the build environment setup script. We can rely
> upon checking for conf/bblayers.conf instead, so use this check.
>
> This does allow BUILDDIR (which is normally set by the environment
> script) to be unset; however if it is set then it is assumed to be the
> correct build directory and will be used in the error message that is
> shown when we can't find conf/bblayers.conf.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Acked-by: Andreas Oberritter <obi@opendreambox.org>
> ---
> scripts/bitbake | 15 ++++++++++-----
> 1 files changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/scripts/bitbake b/scripts/bitbake
> index 1ba1839..f02e89b 100755
> --- a/scripts/bitbake
> +++ b/scripts/bitbake
> @@ -37,6 +37,16 @@ if [ "$py_v26_check" != "True" ]; then
> exit 1
> fi
>
> +if [ ! -e conf/bblayers.conf ] ; then
> + BDPRINT=""
> + [ -n "$BUILDDIR" ] && BDPRINT=": $BUILDDIR"
> + echo "Unable to find conf/bblayers.conf"
> + echo "BitBake must be run from within your build directory$BDPRINT"
> + exit 1
> +elif [ -z "$BUILDDIR" ] ; then
> + BUILDDIR="`pwd`"
> +fi
> +
> needtar="1"
> TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
> float_test() {
> @@ -47,11 +57,6 @@ float_test() {
> # but earlier versions do not
> float_test "$TARVERSION > 1.23" && needtar="0"
>
> -if [ "`pwd`" != "$BUILDDIR" ] ; then
> - echo "BitBake must be run from your build directory: $BUILDDIR"
> - exit 1
> -fi
> -
> buildpseudo="1"
> if [ $needpseudo = "1" ]; then
> if [ -e "$BUILDDIR/pseudodone" ]; then
next prev parent reply other threads:[~2012-03-27 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 11:50 [PATCH 0/3] Fixes for bitbake wrapper script Paul Eggleton
2012-03-27 11:50 ` [PATCH 1/3] scripts/bitbake: try harder to check if pseudo exists Paul Eggleton
2012-03-27 13:08 ` Andreas Oberritter
2012-03-27 13:14 ` Paul Eggleton
2012-03-27 11:50 ` [PATCH 2/3] scripts/bitbake: allow switching between build directories Paul Eggleton
2012-03-27 13:09 ` Andreas Oberritter [this message]
2012-03-27 11:50 ` [PATCH 3/3] scripts/bitbake: add/fix some comments Paul Eggleton
2012-03-27 13:09 ` Andreas Oberritter
2012-03-31 15:45 ` [PATCH 0/3] Fixes for bitbake wrapper script Paul Eggleton
2012-04-03 23:33 ` Saul Wold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F71BBF7.4030001@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox