Can't compile "Debug" configuration for ESP8226 and IotWebConf

[Scavanger]

Hello,
I’m trying to get NodeMCU (NodeMCU_1_0 ESP-12E_Module) running with the IotWebConf library, unfortunately I can’t compile a debug configuration, I get the following “undefined reference error” message:

Waiting for code model update to complete...
Launching Arduino builder...
Run "C:\Users\andi__000\AppData\Local\VisualGDB\Arduino\arduino-builder.exe -prefs=com.sysprogs.extraflags="-DGDBSTUB_BREAK_ON_INIT=1" -compile -logger=machine -fqbn=esp8266:esp8266:nodemcuv2:xtal=80,vt=flash,exception=disabled,stacksmash=disabled,ssl=all,mmu=3232,non32xfer=fast,eesz=4M2M,led=2,ip=lm2f,dbg=Disabled,lvl=None____,wipe=none,baud=115200 -build-path E:\RC-Dev\ArduinoESP8226Test\Output\NodeMCU_1_0__ESP-12E_Module_\Debug -unoptimize=sketch -hardware E:\Dokumente/Arduino/hardware -hardware E:\Dokumente/ArduinoData/packages -hardware C:\Users\andi__000\AppData\Local/Arduino15/packages -tools E:\Dokumente/ArduinoData/packages -tools C:\Users\andi__000\AppData\Local/Arduino15/packages -libraries E:\Dokumente/Arduino/Libraries -prefs=runtime.tools.xtensa-lx106-elf-gcc.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\xtensa-lx106-elf-gcc\3.0.4-gcc10.3-1757bed -prefs=runtime.tools.python3.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\python3\3.7.2-post1 -prefs=runtime.tools.mkspiffs.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\mkspiffs\3.0.4-gcc10.3-1757bed -prefs=runtime.tools.ctags.path=C:\Users\andi__000\AppData\Local\VisualGDB\Arduino\tools-builder\ctags\5.8-arduino11 sketches/ArduinoESP8226Test.ino" in directory "E:\RC-Dev\ArduinoESP8226Test" on local computer
C:\Users\andi__000\AppData\Local\VisualGDB\Arduino\arduino-builder.exe -prefs=com.sysprogs.extraflags="-DGDBSTUB_BREAK_ON_INIT=1" -compile -logger=machine -fqbn=esp8266:esp8266:nodemcuv2:xtal=80,vt=flash,exception=disabled,stacksmash=disabled,ssl=all,mmu=3232,non32xfer=fast,eesz=4M2M,led=2,ip=lm2f,dbg=Disabled,lvl=None____,wipe=none,baud=115200 -build-path E:\RC-Dev\ArduinoESP8226Test\Output\NodeMCU_1_0__ESP-12E_Module_\Debug -unoptimize=sketch -hardware E:\Dokumente/Arduino/hardware -hardware E:\Dokumente/ArduinoData/packages -hardware C:\Users\andi__000\AppData\Local/Arduino15/packages -tools E:\Dokumente/ArduinoData/packages -tools C:\Users\andi__000\AppData\Local/Arduino15/packages -libraries E:\Dokumente/Arduino/Libraries -prefs=runtime.tools.xtensa-lx106-elf-gcc.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\xtensa-lx106-elf-gcc\3.0.4-gcc10.3-1757bed -prefs=runtime.tools.python3.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\python3\3.7.2-post1 -prefs=runtime.tools.mkspiffs.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\mkspiffs\3.0.4-gcc10.3-1757bed -prefs=runtime.tools.ctags.path=C:\Users\andi__000\AppData\Local\VisualGDB\Arduino\tools-builder\ctags\5.8-arduino11 sketches/ArduinoESP8226Test.ino
e:/dokumente/arduinodata/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.4-gcc10.3-1757bed/bin/../lib/gcc/xtensa-lx106-elf/10.3.0/../../../../xtensa-lx106-elf/bin/ld.exe: E:\RC-Dev\ArduinoESP8226Test\Output\NodeMCU_1_0__ESP-12E_Module_\Debug\sketch\ArduinoESP8226Test.ino.cpp.o: in function 

_ZN9DNSServerD2Ev’:
E:\Dokumente\ArduinoData\packages\esp8266\hardware\esp8266\3.0.2\libraries\DNSServer\src/DNSServer.h:52: undefined reference to `_ZTVN10iotwebconf17WebRequestWrapperE’
collect2.exe: error: ld returned 1 exit status
exit status 1
————————————————————-
Command exited with code 1
Executable: C:\Users\andi__000\AppData\Local\VisualGDB\Arduino\arduino-builder.exe
Arguments: -prefs=com.sysprogs.extraflags=”-DGDBSTUB_BREAK_ON_INIT=1″ -compile -logger=machine -fqbn=esp8266:esp8266:nodemcuv2:xtal=80,vt=flash,exception=disabled,stacksmash=disabled,ssl=all,mmu=3232,non32xfer=fast,eesz=4M2M,led=2,ip=lm2f,dbg=Disabled,lvl=None____,wipe=none,baud=115200 -build-path E:\RC-Dev\ArduinoESP8226Test\Output\NodeMCU_1_0__ESP-12E_Module_\Debug -unoptimize=sketch -hardware E:\Dokumente/Arduino/hardware -hardware E:\Dokumente/ArduinoData/packages -hardware C:\Users\andi__000\AppData\Local/Arduino15/packages -tools E:\Dokumente/ArduinoData/packages -tools C:\Users\andi__000\AppData\Local/Arduino15/packages -libraries E:\Dokumente/Arduino/Libraries -prefs=runtime.tools.xtensa-lx106-elf-gcc.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\xtensa-lx106-elf-gcc\3.0.4-gcc10.3-1757bed -prefs=runtime.tools.python3.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\python3\3.7.2-post1 -prefs=runtime.tools.mkspiffs.path=E:\Dokumente\ArduinoData\packages\esp8266\tools\mkspiffs\3.0.4-gcc10.3-1757bed -prefs=runtime.tools.ctags.path=C:\Users\andi__000\AppData\Local\VisualGDB\Arduino\tools-builder\ctags\5.8-arduino11 sketches/ArduinoESP8226Test.ino
Directory: E:\RC-Dev\ArduinoESP8226Test
Command-line action failed
`

The release version compiles correctly.

Thanks for the help.

• This topic was modified 2 years, 9 months ago by Scavanger.
• This topic was modified 2 years, 9 months ago by Scavanger.

[support]

Please note that VisualGDB is a productivity tool for software developers. It can make developers more productive by providing convenient GUI for common time-consuming tasks, and integrating various external tools into Visual Studio, so that they are always a few mouse clicks away.

We are able to offer VisualGDB at affordable price, because we focus on developing and supporting functionality that works the same way for multiple users, hence the development and testing effort is reused between multiple license holders.

We also receive a huge amount of inquiries asking to fix a specific broken project, help make the correct design choice, explain how a specific C++ feature works, or assist porting a library to a different platform. These inquiries require considerable effort to research and communicate the best solution. They do not scale between multiple users. I.e. helping one user solve this type of problem will not automatically help other users. It also does not help the same user avoid the same type of problem in the future. Hence, we are not able to address them within our regular support. If we included this type of help in our support, we would simply not have sufficient resources to provide it at the current license prices, or to allocate any resources to VisualGDB development.

We are happy to offer project-specific help via our consulting service per Zoom, TeamViewer or any other screen sharing service of your choice. We charge a fixed hourly rate for these sessions (billed in 1/2-hour increments), and are happy to solve any problems our users encounter. The rate includes a detailed follow-up email at the end of the session, that includes an overview of the used techniques and a summary of solved problems and future recommendations. Please contact our sales if you need more information about it.

Alternatively, please consider browsing our documentation and tutorials. Our documentation lists most VisualGDB settings, and the tutorials show how to use VisualGDB for in many real-world scenarios. Our technical support is limited to issues in VisualGDB itself, that can be reproduced from scratch per our problem reporting guidelines (i.e. do not depend on external projects that can potentially contain errors).

[Author]

Posts