4 ms·
It's 14Mb with 400+ libraries included. `cargo bloat` shows that top function by size is from rustls (SSL support). For a container with a single binary, it's h
by oneshtein 2y ago
It's 14Mb with 400+ libraries included. `cargo bloat` shows that top function by size is from rustls (SSL support). For a container with a single binary, it's huge space saver. Moreover, I can easily optimize binary by size to 7.9Mb binary (20kb per crate on average).
> because it breaks (broke?) the hashing Yocto does.
It's problem with Yocto. In my case (few years ago, before the war), I just build RPM packages by my own build system and then install them on top of pure Yocto system. I optimize my binaries for embedded by size.
In theory, debug symbols can be separated to a separate debuginfo rpm, and installed only when needed or mounted remotely from a host system. In practice, I just install the binary enhanced for debugging (with debugging and tracing features enabled) directly to Yocto device, then add test case to reproduce the problem on host, because I hate debuggers.