From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] libsdl: support native compilation
Date: Mon, 19 Oct 2015 16:33:53 +0100 [thread overview]
Message-ID: <1445268833.17974.106.camel@linuxfoundation.org> (raw)
In-Reply-To: <562501BF.6010202@windriver.com>
On Mon, 2015-10-19 at 09:44 -0500, Mark Hatle wrote:
> On 10/19/15 9:17 AM, Dmitry Eremin-Solenikov wrote:
> > qemu-native can use SDL backend for graphical output. Currently it is
> > expected to use libsdl provided by the host. However this can lead to
> > library incompatibilities between host and target. Make libsdl recipe
> > support native compilation.
>
> I don't object to the patch.. but we did have multiple problems in the past
> where libsdl (native) did not work with the host systems X11 or what-ever.
>
> Various failure conditions about not linking, linking to the wrong libsdl, or
> execution failing are what made us prefer the host system's libsdl -- or simply
> disabling libsdl altogether.
This is my big worry too. I remember a lot of problems trying to build a
libsdl that worked on all of the different linux distros someone might
run on. Previously we found that assuming a working libsdl or disabling
it was much easier.
How wide has the testing if this patch series been?
Cheers,
Richard
next prev parent reply other threads:[~2015-10-19 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 14:17 [PATCH 1/3] libsdl: support native compilation Dmitry Eremin-Solenikov
2015-10-19 14:17 ` [PATCH 2/3] qemu: drop hooking of libsdl from the host Dmitry Eremin-Solenikov
2015-10-19 14:17 ` [PATCH 3/3] local.conf.sample: stop adding libsdl-native to ASSUME_PROVIDED Dmitry Eremin-Solenikov
2015-10-19 14:44 ` [PATCH 1/3] libsdl: support native compilation Mark Hatle
2015-10-19 15:33 ` Richard Purdie [this message]
2015-10-22 13:28 ` Dmitry Eremin-Solenikov
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=1445268833.17974.106.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.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