From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Daiane Angolini <daiane.angolini@freescale.com>,
Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH] gpu-viv-bin-mx6q: Make backend configurable
Date: Mon, 03 Feb 2014 13:13:04 +0100 [thread overview]
Message-ID: <52EF87D0.8000709@pseudoterminal.org> (raw)
In-Reply-To: <52EF80F1.2080500@freescale.com>
On 2014-02-03 12:43, Daiane Angolini wrote:
> 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 -
>
One problem I've had is that modifying DISTRO_FEATURES introduced a lot
of changes all over the place, pulling in some dependencies that didn't
work well. It has been a while since I did this, but I remember having
dependency problems when I switched on directfb (and turned off x11).
However, if you say it should work this way, then I accept that. Maybe
something wrong was on my end. I was initially under the impression that
modifying DISTRO_FEATURES is not recommended.
next prev parent reply other threads:[~2014-02-03 12:10 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
2014-02-03 12:13 ` Carlos Rafael Giani [this message]
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=52EF87D0.8000709@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=daiane.angolini@freescale.com \
--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.