Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
	openembedded-core@lists.openembedded.org
Cc: Martin Kelly <martin@xevo.com>
Subject: Re: [PATCH] libsdl: enable X11 for nativesdk
Date: Tue, 11 Apr 2017 18:14:11 +0100	[thread overview]
Message-ID: <1491930851.12091.30.camel@linuxfoundation.org> (raw)
In-Reply-To: <becb96f0-bc8a-3a91-0649-cab9be51d6dd@gmail.com>

On Tue, 2017-04-11 at 09:34 -0700, akuster808 wrote:
> 
> On 04/06/2017 12:55 PM, Martin Kelly wrote:
> > 
> > From: Martin Kelly <mkelly@xevo.com>
> > 
> > Currently, the following situation fails:
> > 
> > - Build an SDK and image. Make the image support graphics but not
> > X11.
> > - Extract SDK and copy image somewhere outside of the Yocto
> > workspace. Do
> >    runqemu on the image.
> > 
> > This results in the error:
> > "Could not initialize SDL(No available video device) - exiting"
> This seems to have fixed an issue I was seeing on FedoraCore 25 with 
> Morty with the same error.  Did I miss comments regarding these
> changes?

No, I haven't directly commented but these changes do worry me a bit in
that we're setting the PACKAGECONFIG to x11 for some nativesdk things
and ignoring it for others. I don't like the inconsistency.

I'm hoping the patch from Jussi today will be a better solution for
this problem, at least for master.

Cheers,

Richard


  reply	other threads:[~2017-04-11 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 19:55 [PATCH] libsdl: enable X11 for nativesdk Martin Kelly
2017-04-11 16:34 ` akuster808
2017-04-11 17:14   ` Richard Purdie [this message]
2017-04-11 21:47     ` Martin Kelly
2017-04-13  0:16       ` Martin Kelly

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=1491930851.12091.30.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster808@gmail.com \
    --cc=martin@xevo.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