From: Adrian Ratiu <adrian.ratiu@collabora.com>
To: Kang Kai <Kai.Kang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] cogl-1.0.inc: set RDEPENDS_${PN}-dev = ""
Date: Wed, 17 Jul 2019 13:46:10 +0300 [thread overview]
Message-ID: <87ftn5ey6l.fsf@collabora.com> (raw)
In-Reply-To: <a1a87489-5023-2ac9-59ee-996725d08a72@windriver.com>
On Wed, 17 Jul 2019, Kang Kai <Kai.Kang@windriver.com> wrote:
Hi
> On 2019/7/17 下午3:48, Adrian Ratiu wrote:
>> ${PN}-dev by default depends on ${PN} but in this case ${PN} is
>> empty by design (FILES_${PN} = "") and is not created, leading
>> to installation dependency errors like the following:
>>
>> Collected errors:
>> * Solver encountered 1 problem(s): * Problem 1/1: * -
>> nothing provides cogl-1.0 = 1.22.2-r0 needed by
>> cogl-1.0-dev-1.22.2-r0.armv7at2hf-neon-imx * * Solution 1: *
>> - do not ask to install a package providing cogl-1.0-dev
>
> I think what you need is
>
> ALLOW_EMPTY_${PN} = "1"
Why is creating and depending on an empty package better than not
creating and depending on it at all?
From what I can see in other recipes both methods are used.
>
>
> Regards,
> Kai
>
>
>>
>> Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
>> ---
>> meta/recipes-graphics/cogl/cogl-1.0.inc | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/meta/recipes-graphics/cogl/cogl-1.0.inc b/meta/recipes-graphics/cogl/cogl-1.0.inc
>> index 3e392fa5ec..a388023a03 100644
>> --- a/meta/recipes-graphics/cogl/cogl-1.0.inc
>> +++ b/meta/recipes-graphics/cogl/cogl-1.0.inc
>> @@ -75,4 +75,6 @@ RPROVIDES_libcogl = "cogl-1.0"
>> RCONFLICTS_libcogl = "cogl-1.0"
>> RREPLACES_libcogl = "cogl-1.0"
>>
>> +RDEPENDS_${PN}-dev = ""
>> +
>> COMPATIBLE_HOST_armv4 = 'null'
>
>
> --
> Kai Kang
next prev parent reply other threads:[~2019-07-17 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 7:48 [PATCH] cogl-1.0.inc: set RDEPENDS_${PN}-dev = "" Adrian Ratiu
2019-07-17 8:18 ` Kang Kai
2019-07-17 10:46 ` Adrian Ratiu [this message]
2019-07-18 1:31 ` Kang Kai
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=87ftn5ey6l.fsf@collabora.com \
--to=adrian.ratiu@collabora.com \
--cc=Kai.Kang@windriver.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