> But beware that they may not be asking for it because they already > have that with the current setup...
For people using only C, Zephyr provides an option to customize the libc build by compiling it along with the application. The barrier here is build time; Zephyr applications are typically fairly small, and libc adds about 1000 source files. If you want libstdc++ with your C++ code, you're stuck with whatever libc and libstdc++ the toolchain provides — libstdc++ is only available as part of the toolchain, bundled with a matching libc. So, yes, people using C can get precisely what they want, but C++ users are pretty stuck with what the toolchain provides. Every library option increases the size of the toolchain. We're currently delivering 35 GCC-based toolchains in a total of 188 different multilib configurations (excluding those created by multilib-space). So we do need to be a bit selective and avoid adding things because someone might want them. Instead we're trying to be responsive to user requests. So, for now at least, we want to provide two library options, -Os -fno-exceptions -fno-asynchronous-unwind-tables and -O2. -- -keith
signature.asc
Description: PGP signature
