public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>, Mark Jonas <toertel@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] libsdl2: Add directfb to PACKAGECONFIG rdepends
Date: Tue, 24 Nov 2020 15:52:31 +0000	[thread overview]
Message-ID: <50edf6012e58b2d75be5c013dcab19365e5e4818.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=URx1WJ9=+7-pQ+iUoTi5yT4jJaPdct0zOqa0gYFTF8Mg@mail.gmail.com>

On Mon, 2020-11-23 at 11:54 -0800, Andre McCurdy wrote:
> On Mon, Nov 23, 2020 at 11:14 AM Mark Jonas <toertel@gmail.com>
> wrote:
> > When building libsdl2 with PACKAGECONFIG[directfb] then directfb is
> > added to the DEPENDS. But the automatically generated runtime
> > dependencies do not add the directfb package to the runtime
> > dependencies. Most likely this happens because libsdl2 does not
> > link
> > against directfb but uses dlopen() or similar. Thus, the runtime
> > dependency to directfb needs to be declared explicitly.
> > 
> > Here, a runtime recommendation is used to allow ignoring the
> > runtime
> > dependency using NO_RECOMMENDATIONS.
> 
> Why would anyone want to ignore the runtime dependency?

Agreed, that does seem strange. Whichever way this goes, the patch
shortlog needs to match the commit (it says rdepends right now).

Cheers,

Richard


  reply	other threads:[~2020-11-24 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 19:13 [PATCH] libsdl2: Add directfb to PACKAGECONFIG rdepends Mark Jonas
2020-11-23 19:54 ` [OE-core] " Andre McCurdy
2020-11-24 15:52   ` Richard Purdie [this message]
2020-11-24 19:04     ` Mark Jonas
2020-11-24 19:32 ` [PATCH V2] " Mark Jonas

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=50edf6012e58b2d75be5c013dcab19365e5e4818.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=toertel@gmail.com \
    /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