All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] runqemu: take TMPDIR from bitbake
Date: Mon, 13 Jun 2011 14:16:09 -0700	[thread overview]
Message-ID: <4DF67E19.8060808@intel.com> (raw)
In-Reply-To: <1307985976-22648-1-git-send-email-anders@chargestorm.se>

On 06/13/2011 10:26 AM, Anders Darander wrote:
> The old standard of using /home/anders/openembedded-core/build/tmp as TMPDIR do not work any longer,
> as - is appended to the real TMPDIR. Thus, always take TMPDIR from
> bitbake, unless TMPDIR is set in the environment.
>
> Signed-off-by: Anders Darander<anders@chargestorm.se>

Thanks for this improvement!

Acked-by: Scott Garman <scott.a.garman@intel.com>

> ---
>   scripts/runqemu |   22 +++++++++-------------
>   1 files changed, 9 insertions(+), 13 deletions(-)
>
> diff --git a/scripts/runqemu b/scripts/runqemu
> index a09362c..aa44070 100755
> --- a/scripts/runqemu
> +++ b/scripts/runqemu
> @@ -262,20 +262,16 @@ SPITZ_DEFAULT_ROOTFS="core-image-sato"
>
>   setup_tmpdir() {
>       if [ -z "$TMPDIR" ]; then
> -        if [ "x$BUILDDIR" = "x" -o ! -d "$BUILDDIR/tmp" ]; then
> -            # BUILDDIR unset, try and get TMPDIR from bitbake
> -            type -P bitbake&>/dev/null || {
> -                echo "In order for this script to dynamically infer paths";
> -                echo "to kernels or filesystem images, you either need";
> -                echo "bitbake in your PATH or to source oe-init-build-env";
> -                echo "before running this script">&2;
> -                exit 1; }
> -
> -            # We have bitbake in PATH, get TMPDIR from bitbake
> -            TMPDIR=`bitbake -e | grep TMPDIR=\" | cut -d '=' -f2 | cut -d '"' -f2`
> -        else
> -            TMPDIR=$BUILDDIR/tmp
> -        fi
> +        # BUILDDIR unset, try and get TMPDIR from bitbake
> +        type -P bitbake&>/dev/null || {
> +            echo "In order for this script to dynamically infer paths";
> +            echo "to kernels or filesystem images, you either need";
> +            echo "bitbake in your PATH or to source oe-init-build-env";
> +            echo "before running this script">&2;
> +            exit 1; }
> +
> +        # We have bitbake in PATH, get TMPDIR from bitbake
> +        TMPDIR=`bitbake -e | grep TMPDIR=\" | cut -d '=' -f2 | cut -d '"' -f2`
>       fi
>   }
>


-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center



  reply	other threads:[~2011-06-13 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 17:26 [PATCH] runqemu: take TMPDIR from bitbake Anders Darander
2011-06-13 21:16 ` Scott Garman [this message]
2011-06-13 22:22 ` Yury Bushmelev
2011-06-14  5:51   ` Anders Darander
2011-06-14  9:25     ` Yury Bushmelev
2011-06-14 10:33       ` Anders Darander
2011-06-14 10:35         ` Phil Blundell
2011-06-14 11:17           ` Anders Darander

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=4DF67E19.8060808@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.