ESP8266 Community Forum

tve wrote:The patch files are attached to this post.

0001-moved-espfs-at-end-of-irom0-resulting-in-single-flas.patch.txt - Hehe, I actualy sneaked in my own implementation (which is very similar to yours btw) at the time of the library split, so it's in the current esphttpd already.
0002-generate-user1.bin-and-user2.bin-for-OTA-update.patch.txt - I'll see what I can do. Tbh I don't want to make the esphttpd example more complex than it needs to be, and with the split of libesphttpd, this is sort-of not in the core of esphttpd anymore. OTA upgrading would still be very nice tho', so I may throw it into the example anyway.
0003-remove-4KB-alignment-of-espfs-reflashing-doesn-t-wor.patch.txt - not sure if I need this

For these:
0004-rewrote-flash-handlers.patch.txt -
0005-add-firmware-validity-sanity-check.patch.txt
0006-added-shell-script-to-reflash-esp.patch.txt
I'll have to modify everything a bit: since libesphttpd now is a module, I can't just throw defines at it.

if you want to support OTA in libesphttpd it seems to me that you need to provide the associated handlers in there. It's then up to the user whether to actually wire up these handlers or not, and that's OK. If they're not wired up GCC will leave them out of the binary, so no harm done.

tve wrote:if you want to support OTA in libesphttpd it seems to me that you need to provide the associated handlers in there. It's then up to the user whether to actually wire up these handlers or not, and that's OK. If they're not wired up GCC will leave them out of the binary, so no harm done.

That is the basic idea indeed. However, I can imagine many people will start off with the esphttpd example as a starting point or guideline, so I'd rather have it working in there too.