From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Alexandru Niculita <alexnick87@gmail.com>,
openembedded <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] libsdl: Add support for libsdl-native
Date: Tue, 28 Jan 2014 00:35:49 +0000 [thread overview]
Message-ID: <1390869349.21652.71.camel@ted> (raw)
In-Reply-To: <2100717.4T6aPSkm6s@peggleto-mobl5.ger.corp.intel.com>
On Mon, 2014-01-27 at 22:50 +0000, Paul Eggleton wrote:
> On Monday 27 January 2014 22:29:09 Andrei Gherzan wrote:
> > On Jan 27, 2014 12:20 PM, "Alexandru Niculita" <alexnick87@gmail.com> wrote:
> > > Hi,
> > >
> > > I could not find a way to avoid using TexturePacker.
> > > TexturePacker is used by XMBC to compile all images used
> > > in a skin into a single file.
> > >
> > > I took the info from here:
> > http://wiki.xbmc.org/index.php?title=TexturePacker
>
> Without having looked at the source code, they don't give much in the way of
> detail as to what it actually does. I wonder if it could be replicated with a
> python script using PIL or similar.
>
> > Would be great to have this soon so we can have xbmc support.
>
> Well, if we truly have to have libsdl-native then we have to find a way to
> mitigate the QEMU problems that building that will trigger, which probably
> means preventing it from finding that in the sysroot. I'm not sure whether this
> will be an acceptable solution from an OE-Core perspective but I can't think
> of any other (other than writing an equivalent to TexturePacker that doesn't
> use SDL or anything that requires SDL).
We'll probably have to put libsdl-native into a special directory and
teach xmbc's tool to find it in the special path.
Its ugly but we can't break qemu and a world of pain lies in not using
the host system's libsdl...
Cheers,
Richard
prev parent reply other threads:[~2014-01-28 0:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 16:33 [PATCH 1/1] libsdl: Add support for libsdl-native Andrei Gherzan
2013-12-17 16:47 ` Paul Eggleton
2013-12-17 16:51 ` Andrei Gherzan
2013-12-17 16:53 ` Paul Eggleton
2013-12-17 17:01 ` Andrei Gherzan
2014-01-03 14:58 ` Andrei Gherzan
2014-01-13 14:09 ` Paul Eggleton
2014-01-19 18:08 ` Andrei Gherzan
[not found] ` <CA+0k_w968Jt7sQktJnH9PLrxnLqs6pF37S6tba8PYn=QksoqNA@mail.gmail.com>
2014-01-27 20:29 ` Andrei Gherzan
2014-01-27 22:50 ` Paul Eggleton
2014-01-28 0:35 ` 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=1390869349.21652.71.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=alexnick87@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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 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.