Open chansheunglong opened 3 years ago
Very sorry about this. Not going to happen without a major rename pass. I suggest you add #define hal_init LMICHAL_init
in your LMIC project config or on the PlatformIO command line where you define other LMIC options. Don't know when we'll have time to fix it here. Seems like a mistake for both libraries (ESP32 and LMIC) to use unqualified names that are not reserved names in the C standard.
the #define fixed my project, If it does not harm, It could be a default in project config
I have put this on the list to investigate in the next release.
Very sorry about this. Not going to happen without a major rename pass. I suggest you add
#define hal_init LMICHAL_init
in your LMIC project config or on the PlatformIO command line where you define other LMIC options. Don't know when we'll have time to fix it here. Seems like a mistake for both libraries (ESP32 and LMIC) to use unqualified names that are not reserved names in the C standard.
Thanks, this seemed to work for me!
Are there any plans to fix this? Seems weird to "just rename hal_init" moving forward forever.
#define hal_init LMICHAL_init
worked for me
worked for me too
I recently updated the arduino-esp32 to version 2.0 and when compiling the program
Seems like the new version of arduino-esp32 (2.0) will not be compatible with arduino-lmic because of the same definition of a function.
Since ESP32 is quite a popular platform and making LMIC and ESP32 not able to work together is sad news, will it be possible for arduino-lmic to add an option, e.g. #DEFINE_USE_ESP32, to alter the naming of the function so there will be no multiple definition?
The old version of arduino-esp32 (1.6) works with arduino-lmic