Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: what is the value of 'BBPATH ?= ""' in layer.conf?
Date: Sun, 22 Nov 2015 17:38:18 +0800	[thread overview]
Message-ID: <56518D0A.7060007@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1511220426050.13978@localhost>



On 11/22/2015 05:29 PM, Robert P. J. Day wrote:
> On Sun, 22 Nov 2015, Robert Yang wrote:
>
>>
>>
>> On 11/22/2015 05:10 PM, Robert P. J. Day wrote:
>>>
>>>     perusing some wind river layers, and in the layer.conf file here:
>>>
>>> https://github.com/WindRiver-OpenSourceLabs/wr-kernel/blob/LB21_7.0_RCPL0002/conf/layer.conf
>>>
>>> i see the opening snippet:
>>>
>>>     BBPATH ?= ""
>>>     # We have a conf and classes directory, add to BBPATH
>>>     BBPATH := "${LAYERDIR}:${BBPATH}"
>>>
>>> what is the purpose of that initial assignment
>>>
>>>     BBPATH ?= ""
>>
>> There would be a warning when BBPATH is null, but that had been fixed,
>> so we don't need it nowadays.
>>
>> // Robert
>
>    i thought as much, i just wanted to be sure. i am a rabid minimalist
> in that, if a line has no value, it should be removed, mostly to avoid
> confusing people like me. :-) i noticed at least a couple WR-OSL
> layers that had that construct, you can decide if you care enough
> about it to clean it up. thanks for the clarifiation.

Thanks, we have cleaned that up in new release.

// Robert

>
> rday
>


  reply	other threads:[~2015-11-22  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22  9:10 what is the value of 'BBPATH ?= ""' in layer.conf? Robert P. J. Day
2015-11-22  9:17 ` Robert Yang
2015-11-22  9:29   ` Robert P. J. Day
2015-11-22  9:38     ` Robert Yang [this message]
2015-11-23 14:16 ` Mark Hatle

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=56518D0A.7060007@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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