All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Li Wang" <li.wang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] linux-dummy: add empty dependent packages
Date: Wed, 17 Mar 2021 10:08:00 +0800	[thread overview]
Message-ID: <dcf612da-579c-6242-c440-fecc1e235b6f@windriver.com> (raw)
In-Reply-To: <166BB6ABA401E063.22828@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 3291 bytes --]

ping!

Thanks,
LiWang.

On 3/13/2021 05:48, Li Wang wrote:
>
> On 3/12/2021 20:44, Richard Purdie wrote:
>> On Fri, 2021-03-12 at 17:52 +0800, Li Wang wrote:
>>> some kernel includes kernel-image-image and kernel-devicetree packages.
>>> these patckages are defined in kernel.bbclass
>>> but, when use linux-dummy, these packages are not defined.
>>> so, define them as empty packages for avoiding compile error:
>>>
>>> ERROR: Nothing RPROVIDES 'kernel-devicetree'
>>>
>>> Signed-off-by: Li Wang <li.wang@windriver.com>
>>> ---
>>>   meta/classes/linux-dummy.bbclass         | 26 
>>> ++++++++++++++++++++++++++
>>>   meta/recipes-kernel/linux/linux-dummy.bb |  2 +-
>>>   2 files changed, 27 insertions(+), 1 deletion(-)
>>>   create mode 100644 meta/classes/linux-dummy.bbclass
>>>
>>> diff --git a/meta/classes/linux-dummy.bbclass 
>>> b/meta/classes/linux-dummy.bbclass
>>> new file mode 100644
>>> index 0000000..cd87915
>>> --- /dev/null
>>> +++ b/meta/classes/linux-dummy.bbclass
>>> @@ -0,0 +1,26 @@
>>> +
>>> +python __anonymous () {
>>> +    if d.getVar('PREFERRED_PROVIDER_virtual/kernel') == 'linux-dummy':
>>> +        # copy part codes from kernel.bbclass
>>> +        kname = d.getVar('KERNEL_PACKAGE_NAME') or "kernel"
>>> +
>>> +        # set an empty package of kernel-devicetree
>>> +        d.appendVar('PACKAGES', ' %s-devicetree' % kname)
>>> +        d.setVar('ALLOW_EMPTY_%s-devicetree' % kname, '1')
>>> +
>>> +        # Merge KERNEL_IMAGETYPE and KERNEL_ALT_IMAGETYPE into 
>>> KERNEL_IMAGETYPES
>>> +        type = d.getVar('KERNEL_IMAGETYPE') or ""
>>> +        alttype = d.getVar('KERNEL_ALT_IMAGETYPE') or ""
>>> +        types = d.getVar('KERNEL_IMAGETYPES') or ""
>>> +        if type not in types.split():
>>> +            types = (type + ' ' + types).strip()
>>> +        if alttype not in types.split():
>>> +            types = (alttype + ' ' + types).strip()
>>> +
>>> +        # set empty packages of kernel-image-*
>>> +        for type in types.split():
>>> +            typelower = type.lower()
>>> +            d.appendVar('PACKAGES', ' %s-image-%s' % (kname, 
>>> typelower))
>>> +            d.setVar('ALLOW_EMPTY_%s-image-%s' % (kname, 
>>> typelower), '1')
>>> +}
>>> +
>> Rather than generating broken empty packages, why not just set 
>> RPROVIDES_${PN}
>> with the appropriate things?
>
> linux-dummy is just an empty package, what does it PROVIDE the 
> appropriate things?
>
> linux-dummy has the similar codes:
>
> =====
>
> oe-core/meta/recipes-kernel/linux/linux-dummy.bb
>
> PACKAGES += "kernel-modules kernel-vmlinux"
> FILES_kernel-modules = ""
> ALLOW_EMPTY_kernel-modules = "1"
> DESCRIPTION_kernel-modules = "Kernel modules meta package"
> FILES_kernel-vmlinux = ""
> ALLOW_EMPTY_kernel-vmlinux = "1"
> DESCRIPTION_kernel-vmlinux = "Kernel vmlinux meta package"
>
> =====
>
> I can offer a more complete empty package as above sample.(FILES_* 
> DESCRIPTION_*)
>
> please give me some suggest about it.
>
> Thanks,
> LiWang.
>
>>
>> Cheers,
>>
>> Richard
>>
>
> 
>

[-- Attachment #2: Type: text/html, Size: 6258 bytes --]

      parent reply	other threads:[~2021-03-17  2:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12  9:52 [OE-core][PATCH] linux-dummy: add empty dependent packages Li Wang
2021-03-12 12:44 ` Richard Purdie
2021-03-12 21:48   ` Li Wang
     [not found]   ` <166BB6ABA401E063.22828@lists.openembedded.org>
2021-03-17  2:08     ` Li Wang [this message]

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=dcf612da-579c-6242-c440-fecc1e235b6f@windriver.com \
    --to=li.wang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.