URL
https://opencores.org/ocsvn/or1k/or1k/trunk
Subversion Repositories or1k
[/] [or1k/] [trunk/] [linux/] [uClibc/] [README] - Rev 1325
Go to most recent revision | Compare with Previous | Blame | View Log
uClibc - a Small C Library for LinuxErik Andersen <andersen@codepoet.org>developing embedded Linux systems. It is much smaller than theGNU C Library, but nearly all applications supported by glibcalso work perfectly with uClibc. Porting applications from glibcto uClibc typically involves just recompiling the source code.uClibc even supports shared libraries and threading. It currentlysystems with support for alpha, ARM, cris, e1, h8300, i386, i960,m68k, microblaze, mips/mipsel, PowerPC, SH, SPARC, and v850processors.If you are building an embedded Linux system and you find thatglibc is eating up too much space, you should consider usinguClibc. If you are building a huge fileserver with 12 Terabytesof storage, then using glibc may make more sense. Unless, forexample, that 12 Terabytes will be Network Attached Storage andyou plan to burn Linux into the system's firmware...uClibc is maintained by Erik Andersen and is licensed under theGNU LIBRARY GENERAL PUBLIC LICENSE . This license allows you tomake closed source commercial applications using an unmodifiedversion of uClibc (Please consider sharing some of the money youmake ;-). You do not need to give away all your source code justbecause you use uClibc and/or run on Linux. You should, however,carefuly review the license and make certain you understand andabide by it strictly.For installation instructions, see the file INSTALL.uClibc strives to be standards compliant, which means that mostdocumentation written for SuSv3, or for glibc also applies touClibc functions. However, many GNU extensions are not supportedbecause they have not been ported, or more importantly, wouldincrease the size of uClibc disproportional to the addedfunctionality. There is some discussion of these differencesin the "docs" directory.Additional information (recent releases, FAQ, mailing list, bugs,etc.) can be found at http://www.uclibc.org/.uClibc may be freely modified and distributed under the terms ofthe GNU Library General Public License, which can be found in thefile COPYING.LIB.Please Note:There is an unwholesomely huge amount of code out therethat depends on the presence of GNU libc header files.We have GNU libc compatible header files. So we havecommitted a horrible sin in uClibc. We _lie_ and claimto be GNU libc in order to force these applications towork as their developers intended. This is IMHO,pardonable, since these defines are not really intendedto check for the presence of a particular library, butrather are used to define an _interface_. Some programsare especially chummy with glibc, and may need thisbehavior disabled by adding CFLAGS+=-D__FORCE_NOGLIBCIf you want to make special exceptions in your code which arespecifically for uClibc, you can make certain to include features.h,and then have your code check for uClibc as follows:#ifdef __UCLIBC__do_something_special();#endifAnd most of all, but sure to have some fun!-Erik
Go to most recent revision | Compare with Previous | Blame | View Log
