All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Bipnesh, Abhinav (Abhinav)" <abhinavbipnesh@avaya.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Graceful continue if some recipe has error
Date: Mon, 16 Feb 2015 18:20:32 +0000	[thread overview]
Message-ID: <7054167.eXFi0SgPrx@peggleto-mobl5.ger.corp.intel.com> (raw)
In-Reply-To: <F38A866CD026F746A3BF0928A84397BE3A351461@AZ-FFEXMB01.global.avaya.com>

On Monday 16 February 2015 17:42:02 Bipnesh, Abhinav wrote:
> Paul Eggleton wrote:
> > On Monday 16 February 2015 17:05:32 Bipnesh, Abhinav wrote:
> > > We have written recipe for our application which reads some
> > > environment variables and follow a path. But if these variables are
> > > not set then recipe parsing results into error. So I was looking if we
> > > can have some way for a graceful continuation. As we want if those
> > > variables are set then it bitbake should continue with rest of
> > > building. So is there way we can achieve the same.
> > 
> > Depends, how are you reading the variables? From python or shell?
>
> I am using python function as below
> python __anonymous () {
>     origenv = d.getVar("BB_ORIGENV", False)
> . . .
> }

Presumably then you would do:

value = origenv.getVar("BAR", False)
if value:
    # do something if set
else:
    # do something if not set

?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2015-02-16 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 17:05 Graceful continue if some recipe has error Bipnesh, Abhinav (Abhinav)
2015-02-16 17:39 ` Paul Eggleton
2015-02-16 17:42   ` Bipnesh, Abhinav (Abhinav)
2015-02-16 18:20     ` Paul Eggleton [this message]

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=7054167.eXFi0SgPrx@peggleto-mobl5.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=abhinavbipnesh@avaya.com \
    --cc=yocto@yoctoproject.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.