All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:43:27 +0300	[thread overview]
Message-ID: <20190805064327.GD4799@localhost> (raw)
In-Reply-To: <f7fa211f-7552-4515-ba7e-7f0d82c96922@www.fastmail.com>

On Mon, Aug 05, 2019 at 04:01:57PM +0930, Andrew Jeffery wrote:
> 
> 
> On Mon, 5 Aug 2019, at 14:35, Adrian Bunk wrote:
> > 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?
> 
> "dtc" doesn't need to appear in depends for pdbg: "dtc-native" does for the
> purpose of building the devicetrees shipped with the application, but "dtc"
> doesn't and dtc(1) itself isn't required at runtime, rather we just need libfdt,
>...

How do you link with libfdt without the non-native dtc in DEPENDS?

> Thanks for the feedback.
> 
> Andrew

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



  reply	other threads:[~2019-08-05  6:43 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
2019-08-05  6:31   ` Andrew Jeffery
2019-08-05  6:43     ` Adrian Bunk [this message]
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=20190805064327.GD4799@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 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.