make CC=gcc CFLAGS="-Os"
This is important, because some rules will invoke CC for things other than compilation, and the parameters will not make sense and result in an error.
After selecting the C library, all of the code in the root filesystem needs to be compiled with the new compiler, so that code can take advantage of the newer, smaller C library. At this point, it's worth evaluating whether static versus shared libraries are the right choice for the target. Shared libraries work best if the device will have arbitrary code running and if that code isn't known at the time of deployment; for example, the device may expose an API and allow end users or field engineers to write modules. In this case, having the libraries on the device would afford the greatest flexibility for those implementing new features.
Shared libraries also would be a good choice if the system contained many separate programs instead of one or two programs. In this case, having one copy of the shared code would be smaller than the same code duplicated in several files.
Systems with a few programs merit closer consideration. When only a few programs are in use, the best thing to do is create a system each way and compare the resulting size. In most cases, the smaller system is the one with no shared libraries. As an added benefit, systems without shared libraries load and start running programs faster (as there's no linking step), so users benefit from an efficiency perspective as well.
Although there's no magic tool for making a system smaller, there is no shortage of tools to help make a system as small as possible. Furthermore, making Linux “small” is more than reducing the size of the kernel; the root filesystem needs to be examined critically and paired down, as this component usually consumes more space than the kernel. This article concentrated on the executable image size; reducing the memory requirements of the program once it is running constitutes a separate project.
Linux-tiny Patches: www.selenic.com/linux-tiny. A series of small patches to the kernel to reduce the image size and runtime resources. Many of these patches already have made their way into the kernel.
GNU C Library: www.gnu.org/software/libc. The GNU C Standard Library is the canonical implementation of the C library. The need for this to run on nearly every platform with backward compatibility resulted in a Lib C that's bigger than most.
uClibc: www.uclibc.org. A well supported smaller implementation of Lib C.
Newlib: sourceware.org/newlib. Red Hat's small C library.
dietlibc: www.fefe.de/dietlibc. The smallest C library of the bunch. It works well with an existing cross-compiler, as the install creates a “wrapper” program for GCC, invoking it with the right parameters to make building with dietlibc very easy.
Gene Sally has been working with all facets of embedded Linux for the last seven years and is co-host of LinuxLink Radio, the most popular embedded Linux podcast. Gene can be reached at firstname.lastname@example.org.
|diff -u: What's New in Kernel Development||May 06, 2015|
|Chrome-Colored Parakeets||May 05, 2015|
|Mumblehard--Let's End Its Five-Year Reign||May 04, 2015|
|An Easy Way to Pay for Journalism, Music and Everything Else We Like||May 04, 2015|
|When Official Debian Support Ends, Who Will Save You?||May 01, 2015|
|May 2015 Issue of Linux Journal: Cool Projects||May 01, 2015|
- diff -u: What's New in Kernel Development
- Mumblehard--Let's End Its Five-Year Reign
- When Official Debian Support Ends, Who Will Save You?
- Ubuntu Ditches Upstart
- An Easy Way to Pay for Journalism, Music and Everything Else We Like
- Chrome-Colored Parakeets
- "No Reboot" Kernel Patching - And Why You Should Care
- Return of the Mac
- Picking Out the Nouns
- Android Candy: Intercoms