In file included from /Users/ronalexander/Library/CloudStorage/OneDrive-Personal/Documents/Electronics/SourceCode/Arduino/libraries/ESPAsyncWebSrv/src/WebAuthentication.cpp:21: /Users/ronalexander/Library/CloudStorage/OneDrive-Personal/Documents/Electronics/SourceCode/Arduino/libraries/ESPAsyncWebSrv/src/WebAuthentication.h:27:51: error: missing binary operator before token "(" 27 | #if ESP_ARDUINO_VERSION >= ESP_ARDUINO_VERSION_VAL(3, 0, 0) | ^
The bypass is to do a back level from 1.2.8 to 1.2.7 but the macro needs to be properly fixed. I went to github for the library (not github trained) and there is NO Issues thing so I can't post there. I am tagging @ptillisch in order to get the attention of someone who might know how to properly deal with this. @edthewino
Hi @sonofcy. Which version of the "esp32" boards platform are you using? You can determine which version you have installed by looking in the Arduino IDE Boards Manager.
This is unexpected. I am able to reproduce the error when compiling the library using version 1.0.6 of the platform. The reason it occurs with that platform is because that was before the ESP_ARDUINO_VERSION_VAL macro was added to the core in version 2.0.0:
But the error does not occur when I compile the library using the modern version 3.0.7 of the platform.
I'm going to ask you to provide the full verbose output from a compilation.
This procedure is not intended to solve the problem. The purpose is to gather more information.
Please do this:
Select File > Preferences... (or Arduino IDE > Settings... for macOS users) from the Arduino IDE menus. The "Preferences" dialog will open.
Check the box next to "Show verbose output during: ☐ compile" in the "Preferences" dialog.
Click the "OK" button. The "Preferences" dialog will close.
Select Sketch > Verify/Compile from the Arduino IDE menus.
Wait for the compilation to fail.
You will see a "Compilation error: ..." notification at the bottom right corner of the Arduino IDE window. Click the "COPY ERROR MESSAGES" button on that notification.
Open a forum reply here by clicking the "Reply" button.
Click the <CODE/> icon on the post composer toolbar. This will add the forum's code block markup (```) to your reply to make sure the error messages are correctly formatted.
Press the Ctrl+V keyboard shortcut (Command+V for macOS users). This will paste the compilation output into the code block.
Move the cursor outside of the code block markup before you add any additional text to your reply.
Click the "Reply" button to post the output.
In case the output is longer than the forum software will allow to be added to a post, you can instead save it to a .txt file and then attach that file to a reply here.
Select the .txt file you saved from the "Open" dialog.
Click the "Open" button. The dialog will close.
Click the "Reply" button to publish the post.
Alternatively, instead of using the "Upload" icon on the post composer toolbar as described in steps (5) - (7) above, you can simply drag and drop the .txt file onto the post composer field to attach it.
If so, why didn't you mention that? The other topic might have provided the forum helpers with valuable context that would allow us to avoid wasting time investigating the problem.
Ok, I am not git trained, just an old (82) tube jockey. I didn't link back since I thought the error was fairly straightforward. Could you let @edthewino know how to know when it is fixed? I am sure it can be done but don't know how.
Fantastic, now he can get back to the SPIFFS/LittleFS issue, we think the library code uses SPIFFS which is deprecated. Does he ignore that as some have suggested? Or does the 'community' fix that too? @edthewino
This procedure is not intended to solve the problem. The purpose is to gather more information.
) on the post composer toolbar: