Why libblepp depends on bluez-devel?

[LinArcX]

When i saw met your repo, i was so excited that finally found an alternative to bluez that doesn't require dbus API.

But when i wanted to build libblepp, i got this error message:

↳ cmake ..
-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting build type to 'Release' as none was specified.
CMake Error at /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Bluez (missing: BLUEZ_LIBRARY BLUEZ_INCLUDE_DIR)
Call Stack (most recent call first):
  /usr/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  cmake/modules/FindBluez.cmake:65 (find_package_handle_standard_args)
  CMakeLists.txt:52 (find_package)

-- Configuring incomplete, errors occurred!
See also "/home/linarcx/Desktop/libblepp/build/CMakeFiles/CMakeOutput.log".

Seriously? Why libblepp depends on bluez-devel API?

[edrosten]

This doesn't make any use of the dbus API.

It uses various low level functions from Bluez for parsing packets, definitions of packet type codes, error codes, socket types, that sort of thing.