| | 1 | uClibc-ng - a small C Library for Linux |
| | 2 | |
| | 3 | uClibc-ng (aka µClibc-ng/pronounced yew-see-lib-see-next-generation) is a C |
| | 4 | library for developing embedded Linux systems. It is much smaller than the GNU |
| | 5 | C Library, but nearly all applications supported by glibc also work perfectly |
| | 6 | with uClibc-ng. |
| | 7 | |
| | 8 | uClibc-ng is a spin-off of uClibc from http://www.uclibc.org from Erik Andersen |
| | 9 | and others. |
| | 10 | |
| | 11 | Porting applications from glibc to uClibc-ng typically involves just |
| | 12 | recompiling the source code. uClibc-ng even supports shared libraries and |
| | 13 | threading. It currently runs on standard Linux and MMU-less (also known as |
| | 14 | µClinux) systems with support for Alpha, ARC, ARM, Blackfin, CRIS, FR-V, HPPA, |
| | 15 | IA64, KVX, LM32, M68K/Coldfire, Metag, Microblaze, MIPS, MIPS64, NDS32, NIOS2, |
| | 16 | OpenRisc, PowerPC, SuperH, Sparc, Tile, x86, x86_64 and Xtensa processors. |
| | 17 | |
| | 18 | If you are building an embedded Linux system and you find that glibc is eating |
| | 19 | up too much space, you should consider using uClibc-ng. If you are building a |
| | 20 | huge fileserver with 12 Terabytes of storage, then using glibc may make more |
| | 21 | sense. Unless, for example, that 12 Terabytes will be Network Attached Storage |
| | 22 | and you plan to burn Linux into the system's firmware... |
| | 23 | |
| | 24 | uClibc-ng is maintained by Waldemar Brodkorb and is licensed under the GNU |
| | 25 | LESSER GENERAL PUBLIC LICENSE. This license allows you to make closed source |
| | 26 | commercial applications using an unmodified version of uClibc-ng. You do not |
| | 27 | need to give away all your source code just because you use uClibc-ng and/or |
| | 28 | run on Linux. You should, however, carefuly review the license and make certain |
| | 29 | you understand and abide by it strictly. |
| | 30 | |
| | 31 | For installation instructions, see the file INSTALL. |
| | 32 | |
| | 33 | uClibc-ng strives to be standards compliant, which means that most |
| | 34 | documentation written for SuSv3, or for glibc also applies to uClibc-ng |
| | 35 | functions. However, many GNU extensions are not supported because they have |
| | 36 | not been ported, or more importantly, would increase the size of uClibc-ng |
| | 37 | disproportional to the added functionality. |
| | 38 | |
| | 39 | Additional information can be found at https://uclibc-ng.org/. |
| | 40 | |
| | 41 | uClibc-ng may be freely modified and distributed under the terms of the GNU |
| | 42 | Lesser General Public License, which can be found in the file COPYING.LIB. |
| | 43 | |
| | 44 | And most of all, be sure to have some fun! :-) |
| | 45 | -Waldemar |
projects / uclibc-ng.git / blame_incremental