From: Adrian Bunk <bunk@stusta.de>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] dtc: Provide libfdt
Date: Mon, 5 Aug 2019 08:04:55 +0300 [thread overview]
Message-ID: <20190805050455.GA4799@localhost> (raw)
In-Reply-To: <20190805031211.11190-1-andrew@aj.id.au>
On Mon, Aug 05, 2019 at 12:42:11PM +0930, Andrew Jeffery wrote:
> Applications are appearing that depend on parsing flattened devicetree
> in userspace on target devices, e.g. pdbg[1]. Mark dtc as providing
> libfdt so application recipes can depend on it.
>
> [1] https://github.com/open-power/pdbg
Shouldn't runtime dependencies on dtc already be autogenerated in this
case when you have dtc in DEPENDS?
> Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
> ---
> meta/recipes-kernel/dtc/dtc.inc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-kernel/dtc/dtc.inc b/meta/recipes-kernel/dtc/dtc.inc
> index 0650e3c82e6d..d55c8af90660 100644
> --- a/meta/recipes-kernel/dtc/dtc.inc
> +++ b/meta/recipes-kernel/dtc/dtc.inc
> @@ -5,6 +5,8 @@ SECTION = "bootloader"
> LICENSE = "GPLv2 | BSD"
> DEPENDS = "flex-native bison-native"
>
> +PROVIDES += "libfdt"
>...
This should be a proper separate library package, so that applications
depending on it stop pulling in the command line tools.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-08-05 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 3:12 [PATCH] dtc: Provide libfdt Andrew Jeffery
2019-08-05 5:04 ` Adrian Bunk [this message]
2019-08-05 6:31 ` Andrew Jeffery
2019-08-05 6:43 ` Adrian Bunk
2019-08-05 6:46 ` Andrew Jeffery
2019-08-05 16:37 ` Ross Burton
2019-08-06 1:40 ` Andrew Jeffery
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=20190805050455.GA4799@localhost \
--to=bunk@stusta.de \
--cc=andrew@aj.id.au \
--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