Hi Michal, > So what external application should do? Add own copy of headers to > sources or try use BlueZ copy of headers. I think that first option is > better, because build dependency with BlueZ does not make > implementation kernel-safe. I think about user try to use one version > of libpcap and try to change kernel to older (there can be old kernel > API). for libpcap and sockaddr_hci and the HCI_CHANNEL_MONITOR, you should just add your own copy of these structs and defines. Do not even bother copying BlueZ headers. Just create the structs and defines by yourself and use them. We have done this internally inside BlueZ as well a few times. A build or runtime dependency on libbluetooth is a bad idea. You can install libbluetooth if you build BlueZ with —enable-library, but that library will be deprecated at some point. So might well just prepare yourself for it. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
