On 03/22/2012 11:36 AM, Denys Dmytriyenko wrote:
On Thu, Mar 22, 2012 at 11:22:42AM +0800, Robert Yang wrote:
On 03/22/2012 04:27 AM, Richard Purdie wrote:
On Wed, 2012-03-21 at 21:14 +0100, Koen Kooi wrote:
Op 21 mrt. 2012, om 20:42 heeft Saul Wold het volgende geschreven:
On 03/21/2012 07:25 AM, Samuel Stirtzel wrote:
* This move will allow the testing of meta-kde for users without
meta-openembedded.
So what other layers are using giflib?
Your suggesting that we need to have it in oe-core so people don't need to add
the meta-openembedded layer when using meta-kde?
I am just trying to get more data before making a decision.
Let's put everything in oe-core!
Let's try and be constructive ;-).
I think to make a good decision about this we need to understand which
layers use giflib.
Is this really the only component from meta-oe that meta-kde needs? If
Yes, as far as we know, this is the only component from meta-oe that
meta-kde needs.
Are you talking about kdelibs/kdebase or the entire KDE world? Building any of
I just meant the kdebase, a base kde desktop, the kde-workspace which
can start the kde by command "startkde".
// Robert
the standard KDE apps (kdenetwork, kdemultimedia, etc.) will bring additional
dependencies...
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
