You are reading a single comment by @JumJum and its replies. Click here to read the full conversation.
  • First of all before returning back to business, a happy new year !!
    Hope you enjoyed vacation with your family.
    My vacation will start in less than 2 weeks, so let me write some lines before.

    Started porting of GATT Client for ESP32 and found a lot usage of CENTRAL_LINK_COUNT
    What does CENTRAL_LINK_COUNT stand for ? Is it something like "GATT_CLIENT_ENABLED" ?

    In wrapper often is an ifdef NRF52. First I expanded ifdef to support several definitions. This way I could have "ifdef" : "NRF52,ESP32"
    But then I walked into the trap of having sd_ble-functions, which are not available for ESP32. To bypass this I defined new wrapper, for example for defintion of BluetoothDevice in an ESP32 specific file, where main change is ifdef to ESP32.

    Since major part of source in this new file is copy/paste, this is not my favourite solution. Right now it helps me to go on. Any suggestion, how we should go on for the future ? Should we add some more definitions to bluetooth.h ? Other option would be some ifdefs in core functions, which I would not prefer.

    One more point, for me to understand what sd_ble.functions are doing, is different naming. Looks like for NRF connect is used and for ESP32 it is open. Not a big deal, once you know about it. I wonder if there is a general naming convention.

About

Avatar for JumJum @JumJum started