-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build failures 'SemaphoreHandle_t' does not name a type #36
Comments
Hrmm...good point. Since my device works pretty well there was not much need to keep track of lib updates. But I'll check if switching ota lib could be done without too much effort. |
Thanks that would be great!
Peter
…On Sat, 30 Nov 2024 at 18:34, Andreas ***@***.***> wrote:
Hrmm...good point. Since my device works pretty well there was not much
need to keep track of lib updates. But I'll check if switching ota lib
could be done without too much effort.
—
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAP3U5UFFN2QV2NCUPUYOIT2DIAMFAVCNFSM6AAAAABSYOR2EOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBZGEZTKOBYGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
for which board are you compiling? what is your pio run command look like? |
It’s the TTGO T-Display esp32 , not home at the moment but just tried to
build from the pio build menu.
…On Mon, 2 Dec 2024 at 19:25, Andreas ***@***.***> wrote:
for which board are you compiling? what is your pio run command look like?
—
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAP3U5UU6T26222F6AZYJGT2DSX2PAVCNFSM6AAAAABSYOR2EOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJSGU2TIMZTGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I tried switching to ElegantOTA here
|
if you see the SemaphoreHandle_t build error can you paste the complete compile output? |
I'm not sure if I have something wrong on my machine, but this is the output of just trying to build the ESP32_TTGO_DISPLAY target. building in vscode on macos Sequoia 15.0.1, 3.7 GHz 6-Core Intel Core i5
Processing ESP32_TTGO_DISPLAY (platform: espressif32; board: esp32dev; framework: arduino)Verbose mode can be enabled via
Environment Status Duration ESP32_TTGO_DISPLAY FAILED 00:00:30.420
|
indeed strange ... let me for comparison paste beginning of my output that show some difference in pio related version (looks deps pkgs are same version numbers which makes sense ) $ platformio run --environment ESP32_TTGO_DISPLAY
|
are you able to run without vscode, or from cmdline check the version: [notice] A new release of pip is available: 24.2 -> 24.3.1 |
did I quick test based on the first error
test.C:4:14: error: variable or field 'logText' declared void including the Arduino.h seems to resolve this ... need to think about it, I guess I had seen issues like this before |
somehow the toolchains behave a bit different.
|
Failed again, Processing ESP32_TTGO_DISPLAY (platform: espressif32; board: esp32dev; framework: arduino)Verbose mode can be enabled via
23 | #include "wifi_mqtt_creds.h" Environment Status Duration ESP32_TTGO_DISPLAY FAILED 00:00:11.608
|
not sure why mine would behave differently? |
I had little more time ... now my compile fails as well after changing from NimBLE-Arduino to esp-nimble-cpp (that was some suggestion somewhere ;) ) for me looks like this now
|
will need some more time on this later ... sorry not much help so far |
That’s no problem at all, thanks for looking in to it.
Merry Christmas!
…On Fri, 13 Dec 2024 at 10:44, Andreas ***@***.***> wrote:
will need some more time on this later ... sorry not much help so far
—
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAP3U5XWVYKI7VFVAXS2ROT2FK3CHAVCNFSM6AAAAABSYOR2EOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBRGE2DKMJWGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm guessing this is due to the boad api changes over time but I'm getting error: 'SemaphoreHandle_t' does not name a type. when trying to build. I also found that the AsyncElegantOTA library has been deprecated for ElegantOTA - I'm not sure if any code changes are required to move to this library?
The text was updated successfully, but these errors were encountered: