All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.
Date: Wed, 13 Dec 2006 12:48:27 +0100	[thread overview]
Message-ID: <200612131248.27578.openembedded@hrw.one.pl> (raw)
In-Reply-To: <200612130851.38002.openembedded@hrw.one.pl>

Dnia środa, 13 grudnia 2006 08:51, Marcin Juszkiewicz napisał:
> Dnia wtorek, 12 grudnia 2006 22:00, Michael 'Mickey' Lauer napisał:

> > The advantage of Opie fitting into 14.5MB flash like on Sharp SL5500
> > would be void then.

> OPIE from .dev already is hard to fit - qte-mt with Japanese support is
> larger.

16.469.224 opie-image-collie-20061213112019.rootfs.jffs2

Thats openzaurus-unstable/collie build of today. 

OPIE is hard to build from .dev - rtti/no-rtti problems from time to time 
(opie-alarm/qcop/rdesktop are not buildable without linking with g++ or 
changing CFLAGS).

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

             I do not fear computers. I fear the lack of them.
             		-- Isaac Asimov





  reply	other threads:[~2006-12-13 11:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1GuDwk-0002kI-IJ@linuxtogo.org>
2006-12-12 20:31 ` [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE Koen Kooi
2006-12-12 20:47   ` Paul Sokolovsky
2006-12-12 21:00     ` Michael 'Mickey' Lauer
2006-12-12 21:07       ` Koen Kooi
2006-12-13  7:51       ` Marcin Juszkiewicz
2006-12-13 11:48         ` Marcin Juszkiewicz [this message]
2006-12-13 15:18           ` GoXbox Live

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=200612131248.27578.openembedded@hrw.one.pl \
    --to=openembedded@hrw.one.pl \
    --cc=openembedded-devel@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 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.