All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe
Date: Thu, 19 May 2022 22:12:42 +0200	[thread overview]
Message-ID: <d1d9a344-e54d-2418-4a39-95d1eb6882f7@t-online.de> (raw)
In-Reply-To: <CANNYZj8eCxa+4xn_F=h608DjJsSep+gxv3CMqMvSwWWGgpZBXw@mail.gmail.com>

To my knowledge libsdl2 is the  only consumer of libdecor right now. If 
you want to be able to run sdl programs
in windows instead of just having them pasted to the background you 
would want to enable it by default.
I love libsdl so my answer would be ... of course it should be build 
with decoration by default for weston.
But on the other hand ... its mostly useful for games and fun stuff so 
it really depends on your goals.

Markus
> If it is in core, there should be something in core that consumes and
> makes use of it, and preferably automated tests for it. Is this the
> case? Shall weston enable it by default then?
>
> Alex
>
> On Thu, 19 May 2022 at 21:43, Markus Volk <f_l_k@t-online.de> wrote:
>> It doesn't need to be in core, but i would call having window decoration a core component
>> because otherwise things will just not work as expected for weston/gnome-shell. I could also
>> send that recipe to meta-oe if you prefer or just store it in meta-wayland since its wayland related stuff but
>> if you aim to support libsdl in a proper way this recipe should be around somewhere i think.
>> Personally i prefer sway. It has server side decoration and there is no need for libdecor.
>>
>> Markus
>>
>>   Am 19.05.22 um 18:46 schrieb Alexander Kanavin:
>>
>> Also, does this need to be in core (as opposed to meta-oe)? Why?
>>
>> Alex
>>
>> On Thu, 19 May 2022 at 18:43, Luca Ceresoli via lists.openembedded.org
>> <luca.ceresoli=bootlin.com@lists.openembedded.org> wrote:
>>
>> Hi Markus,
>>
>> Il giorno Thu, 19 May 2022 08:43:11 +0200
>> "Markus Volk" <f_l_k@t-online.de> ha scritto:
>>
>> libdecor is a client-side decoration library for Wayland clients. It
>> is used by libsdl2 for window decoration and is required to provide
>> decoration for shells that use client-side decoration such as
>> gnome-shell or weston.
>>
>> Signed-off-by: Markus Volk <f_l_k@t-online.de>
>>
>> I'm afraid we're having an issue with this patch as well:
>>
>> AssertionError:
>> The following recipes do not have a maintainer assigned to them. Please
>> add an entry to meta/conf/distro/include/maintainers.inc file. libdecor
>> (/home/pokybuild/yocto-worker/oe-selftest-debian/build/meta/recipes-graphics/libdecor/libdecor_0.1.0.bb)
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/3547/steps/14/logs/stdio
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3604/steps/15/logs/stdio
>>
>> And also this warning:
>>
>> WARNING: Nothing RPROVIDES 'nativesdk-libdecor' (but
>> virtual:nativesdk:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-graphics/libdecor/libdecor_0.1.0.bb
>> RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for
>> 'nativesdk-libdecor' NOTE: Runtime target 'nativesdk-libdecor' is
>> unbuildable, removing... Missing or unbuildable dependency chain was:
>> ['nativesdk-libdecor'] WARNING: Nothing RPROVIDES
>> 'nativesdk-libdecor-dev' (but
>> virtual:nativesdk:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-graphics/libdecor/libdecor_0.1.0.bb
>> RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for
>> 'nativesdk-libdecor-dev' NOTE: Runtime target 'nativesdk-libdecor-dev'
>> is unbuildable, removing... Missing or unbuildable dependency chain
>> was: ['nativesdk-libdecor-dev']
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/23/builds/5543/steps/12/logs/stdio
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/4571/steps/12/logs/stdio
>>
>> --
>> Luca Ceresoli, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
>>
>>
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#165910): https://lists.openembedded.org/g/openembedded-core/message/165910
>> Mute This Topic: https://lists.openembedded.org/mt/91203655/3618223
>> Group Owner: openembedded-core+owner@lists.openembedded.org
>> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [f_l_k@t-online.de]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>


  reply	other threads:[~2022-05-19 20:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  6:43 [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe Markus Volk
2022-05-19  6:43 ` [meta-oe][RFC PATCH 2/2] libsdl2: rework and cleanup Markus Volk
2022-05-19 14:18   ` [OE-core] " Luca Ceresoli
2022-05-19 14:30     ` Markus Volk
2022-05-19 15:15       ` Alexander Kanavin
2022-05-19 16:43 ` [OE-core] [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe Luca Ceresoli
2022-05-19 16:46   ` Alexander Kanavin
2022-05-19 19:42     ` Markus Volk
2022-05-19 19:59       ` Alexander Kanavin
2022-05-19 20:12         ` Markus Volk [this message]
2022-05-20 12:46   ` Markus Volk
2022-05-21  7:48     ` richard.purdie
2022-05-22  8:48       ` Markus Volk
2022-05-22  9:24         ` richard.purdie
2022-05-22 10:22           ` Markus Volk
2022-05-22 12:12             ` richard.purdie
2022-05-22 17:26               ` Markus Volk
2022-05-23 15:26               ` Markus Volk
2022-05-31 19:06           ` Markus Volk

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=d1d9a344-e54d-2418-4a39-95d1eb6882f7@t-online.de \
    --to=f_l_k@t-online.de \
    --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.