[oe] Splitting up bluez in a sane way, was Re: Task-base is big :(
koen at dominion.kabel.utwente.nl
Sat Sep 15 14:59:57 CEST 2007
Marcin Juszkiewicz schreef:
> Dnia sobota, 15 września 2007, Koen Kooi napisał:
>> Koen Kooi schreef:
>>> Marcin Juszkiewicz schreef:
>>>> Dnia piątek, 14 września 2007, Koen Kooi napisał:
>>>>> What can be done is to make the default bluez-utils build only
>>>>> build bluez-utils* and have seperate recipes for all the 3rdparty
>>>>> stuff it builds:
>>>>> That would solve both buildtime and runtime issues.
>>>>> What do you think?
>>>> bluez-utils-cups, bluez-utils-gstreamer, bluez-utils-alsa? Sounds
>>>> good for me - especially first both.
>>> bluez-utils-cups and bluez-utils-alsa can be done for sure, but I
>>> haven't looked at where gstreamer comes in and if it can be a
>>> seperate package.
>> What do you think of this patch?
> Looks ok - in cups you can disable hid2hci and in both probably few other
> options can be disabled but their compile time is small rather so better
> leave as they are.
> Did you tried to create separate gst-plugin-bluez recipe?
Not yet, I wanted the easy stuff (bluez, alsa) to get seperated first.
More information about the Openembedded-devel