Replies: 1 comment 1 reply
|
I have solved this issue. I was able to build on my office computer. Since I only use VS Code for openHASP I just uninstalled it and deleted all the related directories left over (.platformio, .pio, etc.). Then reinstalled everything. I was now able to build all openHASP projects without errors. Was able to build my CYD 3248s035c 3.5" with an added W5500 module to operate over Ethernet. In case anyone else is doing this, the config I used is below. [env:esp32-3248s035c_4MB_W5500_2] build_flags = ;region -- TFT_eSPI build options ------------------------ ;region -- Ethernet build options ------------------------ |
Uh oh!
There was an error while loading. Please reload this page.
Hello!
I'm going to preface this that I'm not a Visual Studio Code user. I prefer Visual Studio. So if this is a silly question, please excuse me.
I am trying to build openHASP 0.7.0 on Windows according to the instructions. . I've cloned the repository, installed PlatformIO, edited my platformio_override.ini to select user_setups/esp32/*.ini . All according to the instructions.
If I run build on any of the tasks, right after:
Compiling .pio\build\lanbon_l8\src\font\cyrillic\robotocondensed_regular_24_cyrillic.cpp.o
....build errors start:
In file included from src/hasplib.h:30,
from src/hasp/hasp_dispatch.h:7,
from src/hasplib.h:29,
from src/hasp/hasp_attribute.h:7,
from src/hasplib.h:28,
from src/hasp/hasp.h:11,
from src/hasplib.h:27,
from src/mqtt/hasp_mqtt.h:8,
from include/hasp_conf.h:335,
from src/hasplib.h:20,
from src/custom/my_custom_fan_template.cpp:14:
src/hasp/hasp_event.h:15:27: error: variable or field 'event_timer_calendar' declared void
void event_timer_calendar(lv_task_t* task);
^~~~~~~~~
src/hasp/hasp_event.h:15:27: error: 'lv_task_t' was not declared in this scope
src/hasp/hasp_event.h:15:27: note: suggested alternative: 'lv_area_t'
void event_timer_calendar(lv_task_t* task);
They will continue, accumulating some 800 problems, if I let the build continue.
Seems like a library isn't resolving.
I've attached a terminal output of a failed build as "lanbonfail.txt".
lanbonfail.txt
Do I fix this?
The strange thing is that it was working a week ago. I modified a 3.5" CYD by adding a W5500 and was able to compile openHASP with working Ethernet. Except I didn't have a touch screen because I accidentally compiled the resistive version. When I ran the build on the capacitive version, the result was build errors.
I deleted the openHASP project folder, and then re-cloned via GIT, then tried again. Build errors.
I feel like I may be missing something obvious.
Any help would be appreciated.
Thanks!
All reactions