From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Belen Barros Pena <belen.barros.pena@linux.intel.com>,
toaster@yoctoproject.org
Subject: Re: [PATCH] toaster: change TOASTER_CONF to meta-poky
Date: Mon, 29 Feb 2016 15:59:01 +0000 [thread overview]
Message-ID: <1456761541.11498.179.camel@linuxfoundation.org> (raw)
In-Reply-To: <1456760675-47646-1-git-send-email-belen.barros.pena@linux.intel.com>
On Mon, 2016-02-29 at 15:44 +0000, Belen Barros Pena wrote:
> From: Belen Barros Pena <belen.barros.pena@intel.com>
>
> Patch 9d5483c37523ff3d334c98cafb848282b54962cd renames the layer
> within
> the meta-yocto repository to meta-poky. This patch changes the value
> of
> TOASTER_CONF in the toaster set up script to get Toaster to import
> the
> meta-poky/conf/toasterconf.json file.
>
> Signed-off-by: Belen Barros Pena <belen.barros.pena@intel.com>
> ---
> bitbake/bin/toaster | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bitbake/bin/toaster b/bitbake/bin/toaster
> index 72eae64..4e709ab 100755
> --- a/bitbake/bin/toaster
> +++ b/bitbake/bin/toaster
> @@ -248,7 +248,7 @@ fi
> # in the local layers that currently prevent using an arbitrary
> # toasterconf.json
> if [ "$TOASTER_CONF" = "" ]; then
> - TOASTER_CONF="$(dirname $TOASTER)/../../meta
> -yocto/conf/toasterconf.json"
> + TOASTER_CONF="$(dirname $TOASTER)/../../meta
> -poky/conf/toasterconf.json"
> export TOASTER_CONF=$(python -c "import os; print
> os.path.realpath('$TOASTER_CONF')")
> fi
> if [ ! -f $TOASTER_CONF ]; then
Do we still need this or can this be removed given the TEMPLATECONF
code above it in this file? bitbake really shouldn't have OE/Yocto
knowledge ideally.
Cheers,
Richard
next prev parent reply other threads:[~2016-02-29 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 15:44 [PATCH] toaster: change TOASTER_CONF to meta-poky Belen Barros Pena
2016-02-29 15:59 ` Richard Purdie [this message]
2016-02-29 16:23 ` Barros Pena, Belen
2016-02-29 23:13 ` Brian Avery
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=1456761541.11498.179.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=belen.barros.pena@linux.intel.com \
--cc=toaster@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.