From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
"Burton, Ross" <ross.burton@intel.com>
Cc: Christopher Larson <clarson@kergoth.com>,
Otavio Salvador <otavio@ossystems.com.br>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libsdl: Only enable X11 support when the DISTRO supports it
Date: Tue, 15 Mar 2016 11:48:50 +0000 [thread overview]
Message-ID: <1458042530.2804.310.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKoNSWrsjo5=dKX863+=5YKfjnUv-ic1_Q3MzQA-y9pUcg@mail.gmail.com>
On Tue, 2016-03-15 at 08:01 -0300, Otavio Salvador wrote:
> On Mon, Mar 14, 2016 at 6:26 PM, Burton, Ross <ross.burton@intel.com>
> wrote:
> >
> > On 14 March 2016 at 21:23, Otavio Salvador
> > <otavio.salvador@ossystems.com.br> wrote:
> > >
> > > Do you mind to explain to me why?
> > >
> > > I would like to try to see your view on this.
> >
> >
> > libsdl is a good example to be honest. Why does your choice of
> > target
> > distro features decide what libraries the native sdl should use?
> > Respecting
> > them means in this case that you can't have a graphical qemu.
> > Taking it to
> > hypotheticals, just because my target is pure Wayland doesn't mean
> > I expect
> > sdl to build for Wayland without X11, especially if my desktop is
> > X11 based.
>
> I agree with the overall goal here however this means we ought to
> have
> a HOST_DISTRO_FEATURES setting and not ignore it at all.
I think right now there isn't a pressing need for the extra
complications this brings in. Obviously we should watch the situation
carefully though.
Cheers,
Richard
prev parent reply other threads:[~2016-03-15 11:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 18:46 [PATCH] libsdl: Only enable X11 support when the DISTRO supports it Otavio Salvador
2016-03-14 19:12 ` Otavio Salvador
2016-03-14 20:33 ` Burton, Ross
2016-03-14 20:38 ` Otavio Salvador
2016-03-14 20:41 ` Burton, Ross
2016-03-14 20:43 ` Otavio Salvador
2016-03-14 20:46 ` Burton, Ross
2016-03-14 20:55 ` Otavio Salvador
2016-03-14 21:02 ` Burton, Ross
2016-03-14 21:04 ` Otavio Salvador
2016-03-14 21:21 ` Christopher Larson
2016-03-14 21:23 ` Otavio Salvador
2016-03-14 21:26 ` Burton, Ross
2016-03-15 11:01 ` Otavio Salvador
2016-03-15 11:48 ` Richard Purdie [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=1458042530.2804.310.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=otavio@ossystems.com.br \
--cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox