--===============0822364023==
Content-Type: multipart/alternative; boundary=0016e6434aea17c754046d0a8f26
--0016e6434aea17c754046d0a8f26
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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
--0016e6434aea17c754046d0a8f26
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi
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'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't need for my embedded device.=
=A0
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's=A0 pillars can be easily designed in (or out)=
of=A0 a system=A0
Thanks for any info
David
--0016e6434aea17c754046d0a8f26--
--===============0822364023==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
--===============0822364023==--