arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
22.18k stars 4.8k forks source link

Compilation Error #20212

Closed kskenyon closed 10 months ago

kskenyon commented 10 months ago

/Users/private/Tasmota/tasmota/tasmota_xsns_sensor/xsns_62_esp32_mi.ino:106:52: error: expected class-name before '{' token class MI32AdvCallbacks: public NimBLEScanCallbacks { ^ /Users/private/Tasmota/tasmota/tasmota_xsns_sensor/xsns_62_esp32_mi.ino: In function 'void MI32ScanTask(void)': /Users/private/Tasmota/tasmota/tasmota_xsns_sensor/xsns_62_esp32_mi.ino:1067:13: error: 'class NimBLEScan' has no member named 'setScanCallbacks' MI32Scan->setScanCallbacks(&MI32ScanCallbacks,true); ^~~~ /Users/private/Tasmota/tasmota/tasmota_xsns_sensor/xsns_62_esp32_mi.ino: In function 'void MI32ConnectionGetCharacteristics(NimBLERemoteService)': /Users/private/Tasmota/tasmota/tasmota_xsns_sensor/xsns_62_esp32_mi.ino:1190:35: error: 'class NimBLERemoteCharacteristic' has no member named 'getProperties' MI32.conCtx->buffer[i] = chr->getProperties(); // flags as bitfield ^~~~~

PROBLEM DESCRIPTION

A clear and concise description of what the problem is.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

- [ ] If using rules, provide the output of this command: `Backlog Rule1; Rule2; Rule3`:
```lua
  Rules output here:
- [ ] Set `weblog` to 4 and then, when you experience your issue, provide the output of the Console log:
```lua
  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

Staars commented 10 months ago

You have somehow created a build environment, that tries to compile the legacy MI32 driver with the NimBLE-Arduino library. This can not work, as this driver needs esp-nimble-cpp.

So you need to put the unwanted Bluetooth framework to lib_ignore in your personal custom build environment, depending on the BLE driver you want to build.