On Sat, 16 Nov 2024 at 11:56, Guðni Már Gilbert via
lists.openembedded.org <[email protected]>
wrote:
>
> Hi all,
>
> I've thought some more about this issue. I think it is best to remove these 
> two patches I submitted from master-next if you haven't done so already. 
> Using bluez5-native is wrong, I was misunderstanding the 'native' part a 
> little bit.
>
> Moving forward I think there are really only two possible ways to resolve 
> this (both seem quite cumbersome):
>
> 1. Build BlueZ, and it dependencies by using a 'target' Python 3. Then after 
> BlueZ is done building,  Python should somehow be re-configured and re-built 
> in order to compile with bluetooth support.
> 2. Create a new recipe called libbluetooth which modifies BlueZ such that 
> only the lib folder is built. This recipe only packages the library. In this 
> case, we need to create a custom Makefile and a target which only builds the 
> bluetooth library. It should have minimal dependencies. The goal with this 
> approach is to avoid depending on Python at all such that we can avoid 
> building it until we have libbluetooth available for the target build.
>
> In my opinion I prefer option 2. I am thinking if it is worth it to push a 
> patch to upstream BlueZ to better support only building the library. I'll 
> work on this weekend to build the library locally and see what dependencies 
> it needs. If it doesn't depend on glib and dbus, then that's perfect.
>
> For option 1, I am not sure how this can be done. I'm open to any ideas.

I'm not sure I understand why all this complication is needed. Is
there a circular build dependency between target bluez5 and target
python3? Can you show how and where target python is needed by bluez5
at build time?

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#207189): 
https://lists.openembedded.org/g/openembedded-core/message/207189
Mute This Topic: https://lists.openembedded.org/mt/109519521/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to