From: "Joshua Watt" <JPEWhacker@gmail.com>
To: openembedded-core@lists.openembedded.org, anuj.mittal@intel.com
Subject: Re: [OE-core][PATCH] weston: remoting backend requires GStreamer base plugins
Date: Mon, 15 Feb 2021 10:48:42 -0600 [thread overview]
Message-ID: <9cc2852f-dd67-9723-b6ec-9cb89999465b@gmail.com> (raw)
In-Reply-To: <20210212165146.21830-1-JPEWhacker@gmail.com>
Can this please be backported to gatesgarth?
On 2/12/21 10:51 AM, Joshua Watt wrote:
> The remoting backend of weston requires the GStreamer base plugins, so
> add them to the PACAKGECONFIG depends list.
>
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> ---
> meta/recipes-graphics/wayland/weston_9.0.0.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-graphics/wayland/weston_9.0.0.bb b/meta/recipes-graphics/wayland/weston_9.0.0.bb
> index 75f9fb05fd..d60b5e1a35 100644
> --- a/meta/recipes-graphics/wayland/weston_9.0.0.bb
> +++ b/meta/recipes-graphics/wayland/weston_9.0.0.bb
> @@ -73,7 +73,7 @@ PACKAGECONFIG[colord] = "-Dcolor-management-colord=true,-Dcolor-management-color
> # Clients support
> PACKAGECONFIG[clients] = "-Dsimple-clients=all -Ddemo-clients=true,-Dsimple-clients= -Ddemo-clients=false"
> # Virtual remote output with GStreamer on DRM backend
> -PACKAGECONFIG[remoting] = "-Dremoting=true,-Dremoting=false,gstreamer1.0"
> +PACKAGECONFIG[remoting] = "-Dremoting=true,-Dremoting=false,gstreamer1.0 gstreamer1.0-plugins-base"
> # Weston with PAM support
> PACKAGECONFIG[pam] = "-Dpam=true,-Dpam=false,libpam"
> # Weston with screen-share support
prev parent reply other threads:[~2021-02-15 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 16:51 [OE-core][PATCH] weston: remoting backend requires GStreamer base plugins Joshua Watt
2021-02-12 17:59 ` Otavio Salvador
2021-02-12 18:16 ` Joshua Watt
2021-02-15 16:48 ` Joshua Watt [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=9cc2852f-dd67-9723-b6ec-9cb89999465b@gmail.com \
--to=jpewhacker@gmail.com \
--cc=anuj.mittal@intel.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