From: "Max Krummenacher" <max.oss.09@gmail.com>
To: Diego Sueiro <diego.sueiro@arm.com>,
openembedded-core@lists.openembedded.org
Cc: nd@arm.com
Subject: Re: [OE-core] [PATCH] u-boot: set SYSROOT_DIRS to /boot and ${sysconfdir}
Date: Fri, 18 Dec 2020 10:51:47 +0100 [thread overview]
Message-ID: <64c6a1da3b14ede2c4001a3d2e485bc54e702512.camel@gmail.com> (raw)
In-Reply-To: <51459a27f768a62cab37aabf5a5253e2756a0644.1608204009.git.diego.sueiro@arm.com>
Hi
Am Donnerstag, den 17.12.2020, 11:23 +0000 schrieb Diego Sueiro:
> Since do_install is shipping files to /boot and ${sysconfdir}, we can set
> SYSROOT_DIRS to these dirs and allow recipes which depend on u-boot to use its
> installed artifacts from RECIPE_SYSROOT instead of DEPLOY_DIR_IMAGE.
>
> Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
> ---
> meta/recipes-bsp/u-boot/u-boot.inc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-boot/u-boot.inc
> index 251178db33..6af0766571 100644
> --- a/meta/recipes-bsp/u-boot/u-boot.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot.inc
> @@ -266,6 +266,8 @@ FILES_${PN}-env = " \
> "
>
> FILES_${PN} = "/boot ${datadir}"
> +SYSROOT_DIRS = "/boot ${sysconfdir}"
Wouldn't a += be more future proof. I.e. not dropping the directories which are staged by default.
Max
> +
> RDEPENDS_${PN} += "${PN}-env"
>
> do_deploy () {
>
>
next prev parent reply other threads:[~2020-12-18 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 11:23 [PATCH] u-boot: set SYSROOT_DIRS to /boot and ${sysconfdir} Diego Sueiro
2020-12-18 9:51 ` Max Krummenacher [this message]
2021-01-04 8:29 ` [OE-core] " Diego Sueiro
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=64c6a1da3b14ede2c4001a3d2e485bc54e702512.camel@gmail.com \
--to=max.oss.09@gmail.com \
--cc=diego.sueiro@arm.com \
--cc=nd@arm.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox