All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daiane Angolini <daiane.angolini@freescale.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	Carlos Rafael Giani <dv@pseudoterminal.org>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH] gpu-viv-bin-mx6q: Make backend configurable
Date: Mon, 3 Feb 2014 09:43:45 -0200	[thread overview]
Message-ID: <52EF80F1.2080500@freescale.com> (raw)
In-Reply-To: <CAP9ODKqS5z_ZJ0p4=asaec_FJ5gTToMaM4rF9EZ5AOMmeVUQtQ@mail.gmail.com>

On 03-02-2014 09:34, Otavio Salvador wrote:
> Hello Carlos,
>
> On Mon, Feb 3, 2014 at 9:30 AM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> On 2014-02-03 12:23, Otavio Salvador wrote:
>>> On Mon, Feb 3, 2014 at 8:41 AM, Carlos Rafael Giani
>>> <dv@pseudoterminal.org> wrote:
>>>>
>>>> With this change, the user can set USE_X11 etc. in local.conf to
>>>> override the recipe's DISTRO_FEATURES based choice. This is for example
>>>> beneficial when both X11 and wayland are supported, or when the user
>>>> wants to make use of the regular framebuffer backend. (Modifying
>>>> the distro features list may have far reaching consequences.)
>>>>
>>>> Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
>>>
>>> The Wayland and X11 backends  are not usable at same time as you need
>>> to build apps with different flags. Do you have an usecase in mind?
>>>
>>
>> For example, when I wanted to try out the framebuffer EGL backend of the
>> eglvivsink element in gstreamer-imx , I had to modify the
>> gpu-viv-bin-mx6q.inc file to force it to not install the X11 binaries. (Same
>> when I tried to develop a directfb EGL backend, which I postponed for now,
>> because there are zero docs and examples on how to actually do this.) I will
>> also need it later, when I start working on the Wayland backend. I also
>> needed it when trying to build an xbmc fork with imx extras ; it can only
>> render to framebuffer, not to X11.
>>
>> I agree though that a switch-like statement would be better, but I am not
>> sure how to implement that properly (my OE foo is not that high :) )
>
> The idea here is you to set:
>
> DISTRO_FEATURES_remove = "x11 wayland"
>
> in your local.conf and you'll get a 'framebuffer' system.
>
> Adding also:
>
> DISTRO_FEATURES += "directfb"
>
> gets you a 'DirectFB' system.

You mean, for DirectFB the needed code is:

	DISTRO_FEATURES_remove = "x11 wayland"
	DISTRO_FEATURES += "directfb"


So, both lines together.

If you only include directfb in DISTRO_FEATURES what probably will 
happen is an explosion due to universe collapse (x11+wayland+direcftb)

I know you said the same thing in your email, Otavio. But at first, it 
confused me. So I'm being redundant - just in case -






>
> Is it what you are looking for?
>
>


-- 
Daiane



  reply	other threads:[~2014-02-03 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 10:41 [meta-fsl-arm][PATCH] gpu-viv-bin-mx6q: Make backend configurable Carlos Rafael Giani
2014-02-03 11:23 ` Otavio Salvador
2014-02-03 11:30   ` Carlos Rafael Giani
2014-02-03 11:34     ` Otavio Salvador
2014-02-03 11:43       ` Daiane Angolini [this message]
2014-02-03 12:13         ` Carlos Rafael Giani
2014-02-03 12:09           ` Daiane Angolini

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=52EF80F1.2080500@freescale.com \
    --to=daiane.angolini@freescale.com \
    --cc=dv@pseudoterminal.org \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.