All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Marcin Juszkiewicz <openembedded@hrw.one.pl>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: get rid of virtual/libsdl
Date: Mon, 8 Jan 2007 23:40:54 +0200	[thread overview]
Message-ID: <837928192.20070108234054@gmail.com> (raw)
In-Reply-To: <200701082227.08898.openembedded@hrw.one.pl>

Hello Marcin,

Monday, January 8, 2007, 11:27:08 PM, you wrote:

> I see more and more reports where people has problems with building SDL
> stuff just because they have 'virtual/libsdl == libsdl-qpe' in build 
> config. We all know that libsdl-qpe is set of hacks applied to hacks 
> which evolved from other hacks and thats that all is in state which no
> one want to have something to do. No one ever sent parts of it upstream,
> no one tried to update it to more recent SDL version etc.

> I would like to have one small change in OE: removal of virtual/libsdl at
> all or some kind of other change which would mark libsdl-qpe as not 
> providing virtual/libsdl at all. 

> Most of SDL stuff in OE builds without problem with libsdl-x11 and most of
> them even works when user with libsdl-qpe tries to use it. But if someone
> tries to build SDL apps with libsdl-qpe then he is hit with linking 
> problems, with '-no-rtti/-rtti' problem etc. I'm tired of it.


  Well, that was one of questions I had in mind: why there're separate
builds of SDL apps for GPE and OPIE - it would be kinda natural to expect
SDL ABI to be the same on both.

  But of course it would be nice if this RFC would let for some time
to do such testing.


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2007-01-08 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 21:27 RFC: get rid of virtual/libsdl Marcin Juszkiewicz
2007-01-08 21:40 ` Paul Sokolovsky [this message]
2007-01-08 22:20   ` Marcin Juszkiewicz
2007-01-08 21:46 ` Koen Kooi
2007-01-08 22:02   ` Paul Sokolovsky
2007-01-08 22:17     ` Koen Kooi
2007-01-14 19:55 ` Koen Kooi

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=837928192.20070108234054@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded@hrw.one.pl \
    /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.