Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tim Orling <timothy.t.orling@linux.intel.com>
To: Jed <jed.openxt@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gtk3: enable wayland banckend
Date: Mon, 17 Dec 2018 10:10:09 -0800	[thread overview]
Message-ID: <18DA3CB1-CC7C-4EB3-A52D-333508FC5779@linux.intel.com> (raw)
In-Reply-To: <20181217180651.16040-1-jed.openxt@gmail.com>



> On Dec 17, 2018, at 10:06 AM, Jed <jed.openxt@gmail.com> wrote:
> 
> It is disabled by default, and required for things like mutter to
> be able to run under Wayland.
> 
> Signed-off-by: Jed <jed.openxt@gmail.com>
> ---
> meta/recipes-gnome/gtk+/gtk+3.inc | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-gnome/gtk+/gtk+3.inc b/meta/recipes-gnome/gtk+/gtk+3.inc
> index 6331a4323c..83967ccb7e 100644
> --- a/meta/recipes-gnome/gtk+/gtk+3.inc
> +++ b/meta/recipes-gnome/gtk+/gtk+3.inc
> @@ -35,6 +35,7 @@ EXTRA_OECONF += " \
>                  --enable-modules \
>                  --disable-cups \
>                  --disable-colord \
> +                 --enable-wayland-backend \

Wouldn’t it be better to check that DISTRO_FEATURES contains wayland and then enable it?

>                  ${@bb.utils.contains("DISTRO_FEATURES", "x11", "", "--disable-gtk-doc", d)} \
>                  "
> 
> -- 
> 2.11.0
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



      parent reply	other threads:[~2018-12-17 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 18:06 [PATCH] gtk3: enable wayland banckend Jed
2018-12-17 18:10 ` Burton, Ross
2018-12-17 19:03   ` Jed Lejosne
2018-12-17 18:10 ` Tim Orling [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=18DA3CB1-CC7C-4EB3-A52D-333508FC5779@linux.intel.com \
    --to=timothy.t.orling@linux.intel.com \
    --cc=jed.openxt@gmail.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