[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Removing kdepimlibs
From:       David Boosalis <david.boosalis () gmail ! com>
Date:       2009-06-23 21:20:24
Message-ID: 870c99310906231420n1f300e4bvc9c175de7476a9ac () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi

I am building KDE base to run on an embedded device.   The device has a
rather  low power  x86 CPU and graphics capabilities.  I would like not
having to build kdepimlibs, but this is a prerequisite for building
kdebase.  I won't be using any kdepim functionality and want to know if
there a way to easily get around this dependency.   Akonadi in kdesupport is
another library that I don't need for my embedded device.

Having  seen the beginnings of KDE for much smaller embedded devices
(Symbian phones)  will future versions of KDE take a more ala cart approach
as to  which of it's  pillars can be easily designed in (or out) of  a
system


Thanks for any info
David

[Attachment #5 (text/html)]

Hi<br><br>I am building KDE base to run on an embedded device.=A0=A0 The de=
vice has a rather=A0 low power=A0 x86 CPU and graphics capabilities.=A0 I w=
ould like not having to build kdepimlibs, but this is a prerequisite for bu=
ilding kdebase.=A0 I won&#39;t be using any kdepim functionality and want t=
o know if there a way to easily get around this dependency. =A0 Akonadi in =
kdesupport is another library that I don&#39;t need for my embedded device.=
=A0 <br>
<br>Having=A0 seen the beginnings of KDE for much smaller embedded devices =
(Symbian phones)=A0 will future versions of KDE take a more ala cart approa=
ch as to=A0 which of it&#39;s=A0 pillars can be easily designed in (or out)=
 of=A0 a system=A0 <br>
<br><br>Thanks for any info<br>David <br><br><br><br>


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]