All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentin Popa <valentin.popa@intel.com>
To: Saul Wold <sgw@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] weston: for fbdev enabled distro feature, change WESTON_NATIVE_BACKEND
Date: Fri, 20 Dec 2013 12:25:45 +0200	[thread overview]
Message-ID: <52B41B29.7080805@intel.com> (raw)
In-Reply-To: <52B39115.2080008@linux.intel.com>

On 12/20/2013 02:36 AM, Saul Wold wrote:
> On 12/19/2013 06:20 AM, Valentin Popa wrote:
>> For builds with fbdev (no drm/kms), set
>> WESTON_NATIVE_BACKEND to "fbdev-backend.so"; doing this,
>> weston-launch will be able to know what backend to use.
>>
>> Signed-off-by: Valentin Popa <valentin.popa@intel.com>
>> ---
>>   meta/recipes-graphics/wayland/weston_1.3.1.bb | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-graphics/wayland/weston_1.3.1.bb 
>> b/meta/recipes-graphics/wayland/weston_1.3.1.bb
>> index d97f6af..4ab2776 100644
>> --- a/meta/recipes-graphics/wayland/weston_1.3.1.bb
>> +++ b/meta/recipes-graphics/wayland/weston_1.3.1.bb
>> @@ -45,7 +45,7 @@ PACKAGECONFIG[x11] = 
>> "--enable-x11-compositor,--disable-x11-compositor,virtual/l
>>   # Headless Weston
>>   PACKAGECONFIG[headless] = 
>> "--enable-headless-compositor,--disable-headless-compositor"
>>   # Weston on framebuffer
>> -PACKAGECONFIG[fbdev] = 
>> "--enable-fbdev-compositor,--disable-fbdev-compositor,udev mtdev"
>> +PACKAGECONFIG[fbdev] = "--enable-fbdev-compositor 
>> WESTON_NATIVE_BACKEND="fbdev-backend.so",--disable-fbdev-compositor,udev 
>> mtdev"
>
> Is this a more general way to do this as suggested by Koen back in May?
>
> +# Needed for weston-launch
> +WESTONBACKEND ??= "fbdev-backend.so"
> +
> +export WESTON_NATIVE_BACKEND = "${WESTONBACKEND}"
>
> See http://patches.openembedded.org/patch/50871/
>
> Sau!
Not sure of the context of that patch, but with this patch we have fbdev 
backend -only- if the user builds with fbdev distro feature.
I've tried to build with both kms and fbdev and failed at compile time 
(bug or feature).
>
>
>>   # weston-launch
>>   PACKAGECONFIG[launch] = 
>> "--enable-weston-launch,--disable-weston-launch,libpam"
>>   # VA-API desktop recorder
>>



  reply	other threads:[~2013-12-20 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 14:20 [PATCH] weston: for fbdev enabled distro feature, change WESTON_NATIVE_BACKEND Valentin Popa
2013-12-20  0:36 ` Saul Wold
2013-12-20 10:25   ` Valentin Popa [this message]
2013-12-20 11:50     ` Burton, Ross

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=52B41B29.7080805@intel.com \
    --to=valentin.popa@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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.