Error with compiling of board WeMos d1 r2 mini

[BertB]

ESPEasy_v2.0.0-dev12
IDE 2.4.0

Arduino: 1.8.3 (Windows 10), Board:"WeMos D1 R2 & mini, 80 MHz, 4M (1M SPIFFS), v2 Prebuilt (MSS=536), Disabled, None, 115200"

WAARSCHUWING: Categorie 'LED' in bibliotheek CHT16K33 LED Matrix Library is niet geldig. Wordt gewijzigd naar 'Uncategorized'
WAARSCHUWING: Categorie 'Input' in bibliotheek MechInputs is niet geldig. Wordt gewijzigd naar 'Uncategorized'
WAARSCHUWING: Categorie 'Input' in bibliotheek SerialSensors is niet geldig. Wordt gewijzigd naar 'Uncategorized'
D:\Tools\Arduino sketches\Schetsboek\ESPEasy_v2.0.0-dev12\Source\ESPEasy\ESPEasy.ino:286:27: fatal error: lwip/tcp_impl.h: No such file or directory

#include "lwip/tcp_impl.h"

^

compilation terminated.

exit status 1
Fout bij het compileren van board WeMos D1 R2 & mini

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

[/code]

[BertB]

I first compiled with 2.3.0, with the above result.
Then I migrated to 2.4.0, no real change
Then I reinstalled 2.3.0. and it compiles again.

Is there a way to get a binary out of Atom? That way I can avoid using Arduino IDE.

[TD-er]

Yep, install the 2.3.0 library of ESP8266 in PlatformIO and Arduino IDE. PlatformIO will then use the Arduino installed libs.
Version 2.4.0 is not yet supported with ESPeasy.
It may be with ESPeasy 2.1, but a lot has to be done for it. The 2.4 version uses more memory, which leaves less for ESPeasy.

Dus helaas pindakaas

[BertB]

Thank you TD-er, but I started with 2.3.0 and I got similar errors.
Therefore, after numerous trying and changing the lib location, I decided to go for 2.4.0.
Without result, so I went back to 2.3.0 Tadaa, it compiled . This is what I call irratic behaviour.

I do almost all updates OTA from the ESPEasy module (the load firmware function)
I possible to do the same with platformio? Or, it it possible to get the bin file of the compiled firmware?

[Domosapiens]

bin file is being created in the .pioenvs folder within the project folder

[BertB]

Thank you