Detailed Description
Body of fl::getEmbeddedFs().
The public API says "embedded storage"; this file is where that maps onto a concrete backend. It includes platforms/embedded_fs.h, which selects exactly one platform fragment — LittleFS on ESP, a no-op elsewhere — so the technology name never reaches fl/, and no platform has to hold an opinion about a filesystem it does not have (#4007).
Everything lands in one translation unit on purpose. The entry point and the backend it pulls in are compiled together into fl.fs.embedded+.cpp.o, so a sketch that never calls getEmbeddedFs() leaves the whole chain unreferenced and the linker drops the object outright. Splitting the entry point from its backend would defeat that: the backend would ride in on platforms+.cpp.o, which every sketch links.
Definition in file embedded_fs.cpp.hpp.
Include dependency graph for embedded_fs.cpp.hpp: This graph shows which files directly or indirectly include this file:Go to the source code of this file.
Namespaces | |
| namespace | fl |
| Base definition for an LED controller. | |
Functions | |
| FsImplPtr | fl::getEmbeddedFs (bool format_on_fail=false) FL_NO_EXCEPT |
| Filesystem backed by the microcontroller's own flash, or null where the platform has none. | |
