无需安装BlueZ库编译简易C语言LE扫描程序的方法

Great question! While you can't completely escape relying on BlueZ's core definitions and functions (your code explicitly uses its structs like hci_le_advertising_report and API calls like hci_le_set_scan_parameters), you don't need to install the full BlueZ package system-wide. Here are actionable workarounds:

1. Compile Against Local BlueZ Source Code #

If you have access to the BlueZ source code, you can build it locally without system-wide installation and point GCC directly to its headers and compiled libraries:

• First, build BlueZ in a local directory (skip the make install step):

  git clone https://git.kernel.org/pub/scm/bluetooth/bluez.git
  cd bluez
  ./configure --prefix=/tmp/bluez-local  # Redirect build output to a temp folder
  make
  

• Then compile your program using the local headers and libraries:

  gcc main.c -o le_scan \
    -I./bluez/lib \  # Path to BlueZ's bluetooth.h, hci.h, etc.
    -L./bluez/src/.libs \  # Path to the compiled libbluetooth.so
    -lbluetooth
  

• To run the executable without system-wide BlueZ, set the runtime library path when launching:

  LD_LIBRARY_PATH=./bluez/src/.libs ./le_scan
  

2. Static Compilation with Prebuilt Static Libraries #

If you don't want to build BlueZ from source, use a prebuilt static version of libbluetooth.a to bundle the library directly into your executable:

• Place the BlueZ header files (bluetooth.h, hci.h, hci_lib.h) in a project subdirectory like ./include, and the static library libbluetooth.a in ./lib.
• Compile with static linking to avoid runtime library dependencies:

  gcc main.c -o le_scan \
    -I./include \
    -L./lib \
    -static \
    -lbluetooth
  

• Alternatively, pass the static library directly as an input to simplify the command:

  gcc main.c ./lib/libbluetooth.a -o le_scan -I./include
  

Key Notes #

• Runtime Requirements: Even with static compilation, your program still needs a system with Bluetooth hardware and kernel support (BlueZ libraries ultimately interface with the kernel's Bluetooth subsystem).
• Cross-Compilation: If targeting a different architecture, you'll need BlueZ headers and libraries built specifically for that platform.
• Extra Dependencies: Some BlueZ functions rely on system libraries like libpthread. If you hit undefined reference errors during compilation, add the required libraries (e.g., -lpthread) to your GCC command.

内容的提问来源于stack exchange，提问作者ArmCoder