All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Khem Raj <raj.khem@gmail.com>, meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm][PATCH] meta-arm: Use dynamic layer magic to build trusted-firmware-m
Date: Sun, 5 Jul 2020 17:29:25 -0400	[thread overview]
Message-ID: <20200705212925.GC17660@denix.org> (raw)
In-Reply-To: <70b0c7092890fb9841969d1d0df52b2c9fcccac6.camel@linuxfoundation.org>

On Sun, Jul 05, 2020 at 09:15:45PM +0100, Richard Purdie wrote:
> On Fri, 2020-07-03 at 07:52 -0700, Khem Raj wrote:
> > trusted-firmware-m needs arm binary toolchain to build from another
> > layer, this is the only recipe thus far and its better to hide it to
> > majority users who may not be using trusted-firmware-m and thusly
> > meta-arm-toolchain, folks who need to use trusted-firmware-m should
> > explicitly add it to layer mix
> > 
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > ---
> >  meta-arm/conf/layer.conf                                    | 6 +++++-
> >  .../trusted-firmware-m/trusted-firmware-m_1.0.bb            | 0
> >  2 files changed, 5 insertions(+), 1 deletion(-)
> >  rename meta-arm/{ => dynamic-layers/arm-toolchain}/recipes-bsp/trusted-firmware-m/trusted-firmware-m_1.0.bb (100%)
> > 
> > diff --git a/meta-arm/conf/layer.conf b/meta-arm/conf/layer.conf
> > index 10a7951..2d0c49f 100644
> > --- a/meta-arm/conf/layer.conf
> > +++ b/meta-arm/conf/layer.conf
> > @@ -11,6 +11,10 @@ BBFILE_PRIORITY_meta-arm = "6"
> >  
> >  LAYERDEPENDS_meta-arm = " \
> >      core \
> > -    arm-toolchain \
> >  "
> >  LAYERSERIES_COMPAT_meta-arm = "warrior zeus dunfell"
> > +
> > +BBFILES_DYNAMIC += " \
> > +    arm-toolchain:${LAYERDIR}/dynamic-layers/arm-toolchain/*/*/*.bb \
> > +    arm-toolchain:${LAYERDIR}/dynamic-layers/arm-toolchain/*/*/*.bbappend \
> > +"
> > diff --git a/meta-arm/recipes-bsp/trusted-firmware-m/trusted-firmware-m_1.0.bb b/meta-arm/dynamic-layers/arm-toolchain/recipes-bsp/trusted-firmware-m/trusted-firmware-m_1.0.bb
> > similarity index 100%
> > rename from meta-arm/recipes-bsp/trusted-firmware-m/trusted-firmware-m_1.0.bb
> > rename to meta-arm/dynamic-layers/arm-toolchain/recipes-bsp/trusted-firmware-m/trusted-firmware-m_1.0.bb
> 
> Ross asked to add meta-arm to the autobuilder and I agreed on the basis
> it was passing testing. Due to this change all full builds are now red
> again :(
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/11

FWIW, this has been discussed at length here:
https://lists.yoctoproject.org/g/meta-arm/topic/patch_4_6_arm/75033886

-- 
Denys

  reply	other threads:[~2020-07-05 21:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03 14:52 [meta-arm][PATCH] meta-arm: Use dynamic layer magic to build trusted-firmware-m Khem Raj
2020-07-05 20:15 ` Richard Purdie
2020-07-05 21:29   ` Denys Dmytriyenko [this message]
2020-07-06 11:07   ` Ross Burton
2020-07-06 12:30     ` Ross Burton
2020-07-06 17:48       ` Khem Raj
2020-07-06 21:23 ` Ross Burton
2020-07-07 16:47   ` Khem Raj
2020-07-13 17:09   ` Khem Raj
2020-07-14 10:21     ` Ross Burton

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=20200705212925.GC17660@denix.org \
    --to=denis@denix.org \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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.