Embedded C library http://uclibc-ng.org
Manuel Novoa III
14533cd394
Small fix for when threading (I think) was disabled.
|
%!s(int64=22) %!d(string=hai) anos | |
|---|---|---|
| debian | %!s(int64=22) %!d(string=hai) anos | |
| docs | %!s(int64=22) %!d(string=hai) anos | |
| extra | %!s(int64=22) %!d(string=hai) anos | |
| include | %!s(int64=22) %!d(string=hai) anos | |
| ldso | %!s(int64=22) %!d(string=hai) anos | |
| libc | %!s(int64=22) %!d(string=hai) anos | |
| libcrypt | %!s(int64=23) %!d(string=hai) anos | |
| libintl | %!s(int64=22) %!d(string=hai) anos | |
| libm | %!s(int64=22) %!d(string=hai) anos | |
| libnsl | %!s(int64=22) %!d(string=hai) anos | |
| libpthread | %!s(int64=22) %!d(string=hai) anos | |
| libresolv | %!s(int64=23) %!d(string=hai) anos | |
| libutil | %!s(int64=22) %!d(string=hai) anos | |
| test | %!s(int64=22) %!d(string=hai) anos | |
| .cvsignore | %!s(int64=23) %!d(string=hai) anos | |
| COPYING.LIB | %!s(int64=25) %!d(string=hai) anos | |
| Changelog | %!s(int64=22) %!d(string=hai) anos | |
| Changelog.full | %!s(int64=22) %!d(string=hai) anos | |
| INSTALL | %!s(int64=23) %!d(string=hai) anos | |
| Makefile | %!s(int64=22) %!d(string=hai) anos | |
| README | %!s(int64=22) %!d(string=hai) anos | |
| Rules.mak | %!s(int64=22) %!d(string=hai) anos | |
| TODO | %!s(int64=22) %!d(string=hai) anos |
README
uClibc - a Small C Library for Linux
Erik Andersen
uClibc (aka Clibc/pronounced yew-see-lib-see) 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. 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 (also known as Clinux)
systems with support for alpha, ARM, i386, i960, h8300, m68k,
mips/mipsel, PowerPC, SH, SPARC, and v850 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. If you are building a huge fileserver with 12 Terabytes
of storage, then using glibc may be a better choice...
uClibc is maintained by Erik Andersen and is licensed under the
GNU LIBRARY GENERAL PUBLIC LICENSE . This license allows you to
make closed source commercial applications using uClibc (Please
consider sharing some of the money you make ;-). You do not need
to give away all your source code just because you use uClibc
and/or run on Linux.
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 applies to uClibc
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 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.
Please Note:
There is an unwholesomely huge amount of code out there
that depends on the presence of GNU libc header files.
We have GNU libc header files. So we have committed a
horrible sin in uClibc. We _lie_ and claim to be GNU
libc in order to force these applications to work as their
developers intended. This is IMHO, pardonable, since
these defines are not really intended to check for the
presence of a particular library, but rather are used to
define an _interface_. Some programs are especially
chummy with glibc, and may need this behavior disabled
by adding CFLAGS+=-D__FORCE_NOGLIBC