X-Git-Url: http://git.osdn.net/view?a=blobdiff_plain;f=README;h=002b6f9e8304712b83b95dc16a8b80b1dd1fe016;hb=refs%2Fheads%2Frx;hp=5ebe3bda46d22e21a72071fe047041f2782977ae;hpb=e261c8f8e55fccea5e9ae4e26cdb6c837e17304c;p=uclinux-h8%2Fuclibc-ng.git diff --git a/README b/README index 5ebe3bda4..002b6f9e8 100644 --- a/README +++ b/README @@ -1,38 +1,48 @@ - - uClibc - a small libc implementation - Erik Andersen - - -uClibc (aka µClibc/pronounced yew-see-lib-see) is size-optimized -implementation of the standard C library. The primary use is -for developing embedded Linux systems. It is much smaller then -the GNU C Library (glibc), but nearly all applications supported -by glibc also compile and work perfectly with uClibc. Porting -applications from glibc to uClibc typically involves just -recompiling the source code. uClibc even supports shared -libraries and threading. It currently runs on standard Linux -and MMU-less Linux (also known as µClinux) systems on the -following processors: ARM, i386, h8300, m68k, mips, mipsel, -PowerPC, SH, SPARC, and v850. + uClibc-ng - a small C Library for Linux + +uClibc-ng (aka µClibc-ng/pronounced yew-see-lib-see-next-generation) is a C +library for developing embedded Linux systems. It is much smaller than the GNU +C Library, but nearly all applications supported by glibc also work perfectly +with uClibc-ng. + +uClibc-ng is a spin-off of uClibc from http://www.uclibc.org +from Erik Andersen and others. + +Porting applications from glibc to uClibc-ng typically involves just +recompiling the source code. uClibc-ng even supports shared libraries and +threading. It currently runs on standard Linux and MMU-less (also +known as µClinux) systems with support for ARC, ARM, Blackfin, i386, M68K/Coldfire +MIPS, MIPS64, PowerPC, SH, Sparc, X86_64 and XTENSA processors. + +If you are building an embedded Linux system and you find that +glibc is eating up too much space, you should consider using +uClibc-ng. If you are building a huge fileserver with 12 Terabytes +of storage, then using glibc may make more sense. Unless, for +example, that 12 Terabytes will be Network Attached Storage and +you plan to burn Linux into the system's firmware... + +uClibc-ng is maintained by Waldemar Brodkorb and is licensed under the +GNU LESSER GENERAL PUBLIC LICENSE. This license allows you to +make closed source commercial applications using an unmodified +version of uClibc-ng. You do not need to give away all your source code just +because you use uClibc-ng and/or run on Linux. You should, however, +carefuly review the license and make certain you understand and +abide by it strictly. For installation instructions, see the file INSTALL. -This distribution contains a wrapper for gcc and ld that allows -you to use existing toolchains that were targetted for glibc. -See extra/gcc-uClibc/ for information. - -uClibc strives to be standards compliant, which means that most -documentation written for functions in glibc also apply to uClibc -functions. However, many GNU extensions are not supported +uClibc-ng strives to be standards compliant, which means that most +documentation written for SuSv3, or for glibc also applies to +uClibc-ng functions. However, many GNU extensions are not supported because they have not been ported, or more importantly, would -increase the size of uClibc disproportional to the added +increase the size of uClibc-ng disproportional to the added functionality. -Additional information (recent releases, FAQ, mailing list, bugs, -etc.) can be found at http://www.uclibc.org/. - -uClibc may be freely modified distributed under the terms of the -GNU Library General Public License, which can be found in the -file COPYING.LIB. +Additional information can be found at http://www.uclibc-ng.org/. +uClibc-ng may be freely modified and distributed under the terms of +the GNU Lesser General Public License, which can be found in the +file COPYING. +And most of all, be sure to have some fun! :-) + -Waldemar