Replies: 3 comments 4 replies
-
You can delete this. ESP-Mail-Client/src/ESP_Mail_FS.h Lines 63 to 124 in 469f6b6 Also, this in production. ESP-Mail-Client/src/ESP_Mail_FS.h Lines 22 to 23 in 469f6b6 This is optional based on your usage. ESP-Mail-Client/src/ESP_Mail_FS.h Lines 26 to 29 in 469f6b6 |
Beta Was this translation helpful? Give feedback.
-
This is the limitation of library system in Arduino platform that the library installed only in global libraries folder instead of local. Then any inclusion of other headers and sources files and definitions in your sketch cannot be seen from library code. The library cannot see what you defined in your sketch unless the defined macro was made above the inclusion of In case of single header library like simple library that all codes and functions are in only one header file. This kind of library could see your macro defined in your sketch if it defined before library header inclusion. From this reason, your suggestion cannot be implemented in this library which contains multiple headers and C++ sources files. The library configuration needs to be in the library installed location. And you should take responsibility to back up your version config before update the library and replace it after update library. |
Beta Was this translation helpful? Give feedback.
-
thank you so much for keeping update this libarary. With your last release (3.3.3), I noticed that if I disable ENABLE_ERROR_STRING macro, I am getting the following com[ilation error (using IDE): |
Beta Was this translation helpful? Give feedback.
-
Hey Suwatchai,
Thank you so much for your great work on ESP-Mail-Client .
I guess you undersatnd quit well my application executed on ESP8266 with no external memory. I noticed your latest comments for code reduction in the last update ESP-Mail-Client@3.2.5.
I returned yesterday to work on my code. I updated automaically my IDE libarary and lost all of my latest modifications I had made in library files to reduce and optimize my code size.
May I suggest you find a way that all modifications needed for code reduction (for eample: no external memory, no attachments, etc.) will be organized separetally and not in the major library files wich will be replaced on every libarary update cycle?
Beta Was this translation helpful? Give feedback.
All reactions