All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Svein Seldal <sveinse@seldal.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Path to current bb-file or layer
Date: Thu, 21 Sep 2017 22:36:19 +0100	[thread overview]
Message-ID: <1506029779.18640.168.camel@linuxfoundation.org> (raw)
In-Reply-To: <01070f8e-6997-8b16-73f3-baea5a58dc8e@seldal.com>

On Thu, 2017-09-21 at 22:00 +0200, Svein Seldal wrote:
> To determine a image version, I'd like to read a VERSION file which
> is 
> located in the root of the layer. (Per our development procedure.)
> I'd 
> like to read it from a bbclass file. However I seem to be unable to
> find 
> any methods or variables to find a useful path to either the current 
> bb-file or the root of the layer.
> 
> The only way I have found is to parse through BBLAYERS and guess at
> what 
> my own layer is of those, and then use the found to access the file.
> But 
> this feels very wacky.
> 
> Is there a reason why bitbake doesn't have a variable path reference
> to the current file?

You mean like ${FILE} ?

$ bitbake bash -e | grep ^FILE=
FILE="/media/build1/poky/meta/recipes-extended/bash/bash_4.4.bb"

Cheers,

Richard


  parent reply	other threads:[~2017-09-21 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 20:00 Path to current bb-file or layer Svein Seldal
2017-09-21 21:29 ` Andre McCurdy
2017-09-21 21:36 ` Richard Purdie [this message]
2017-09-22  8:17   ` Svein Seldal
2017-09-22  8:30     ` Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2017-09-22 11:04 Svein Seldal
2017-09-22 11:42 ` Richard Purdie
2017-09-22 13:39   ` Svein Seldal

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=1506029779.18640.168.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=sveinse@seldal.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.