From: Trevor Woerner <twoerner@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: bitbake-layers layerindex-fetch
Date: Fri, 29 May 2015 14:21:16 -0400 [thread overview]
Message-ID: <5568AE1C.3010407@gmail.com> (raw)
In-Reply-To: <7025804.ZvuMXxFa1D@peggleto-mobl.ger.corp.intel.com>
Hi Paul,
On 05/26/15 09:51, Paul Eggleton wrote:
> Hi Trevor,
>
> On Friday 22 May 2015 17:57:46 Trevor Woerner wrote:
>> I'm curious to know what heuristic "bitbake-layers layerindex-fetch"
>> uses to determine where to place the fetched layers?
>>
>> I asked my system to:
>>
>> $ bitbake-layers layerindex-fetch meta-qt5
>>
>> and it keeps insisting on installing meta-qt5 and meta-openembedded
>> under my openembedded-core layers resulting in:
>>
>> /z/master/layers/openembedded-core/meta-openembedded/meta-ruby \
>> /z/master/layers/openembedded-core/meta-qt5 \
>>
>> Is there a way that I can tell bitbake-layers that my layers are located
>> at /z/master/layers and have it work from there?
> This is controlled by BBLAYERS_FETCH_DIR; by default this is set to
> "${COREBASE}" with ??= so you can set it to your preferred value in local.conf
> as desired.
Awesome, thanks! :-)
> (We should definitely document this, I acknowledge at the moment it
> isn't documented anywhere.)
>
I've sent a patch for the Bitbake User's Manual.
next prev parent reply other threads:[~2015-05-29 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 21:57 bitbake-layers layerindex-fetch Trevor Woerner
2015-05-26 13:51 ` Paul Eggleton
2015-05-29 18:21 ` Trevor Woerner [this message]
2015-05-29 20:11 ` Trevor Woerner
2015-06-03 8:29 ` Paul Eggleton
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=5568AE1C.3010407@gmail.com \
--to=twoerner@gmail.com \
--cc=bitbake-devel@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 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.