Embedded C library http://uclibc-ng.org
Waldemar Brodkorb
952bb00f0b
Revert "libdl: fix size parameter when unmap library in dlclose"
|
6 gadi atpakaļ | |
|---|---|---|
| docs | 6 gadi atpakaļ | |
| extra | 6 gadi atpakaļ | |
| include | 6 gadi atpakaļ | |
| ldso | 6 gadi atpakaļ | |
| libc | 6 gadi atpakaļ | |
| libcrypt | 6 gadi atpakaļ | |
| libiconv | 7 gadi atpakaļ | |
| libintl | 7 gadi atpakaļ | |
| libm | 6 gadi atpakaļ | |
| libpthread | 6 gadi atpakaļ | |
| librt | 7 gadi atpakaļ | |
| libuargp | 7 gadi atpakaļ | |
| libubacktrace | 7 gadi atpakaļ | |
| libutil | 6 gadi atpakaļ | |
| utils | 6 gadi atpakaļ | |
| .gitignore | 12 gadi atpakaļ | |
| COPYING.LIB | 18 gadi atpakaļ | |
| COPYING.LIB.boilerplate | 18 gadi atpakaļ | |
| INSTALL | 8 gadi atpakaļ | |
| MAINTAINERS | 7 gadi atpakaļ | |
| Makefile | 14 gadi atpakaļ | |
| Makefile.help | 7 gadi atpakaļ | |
| Makefile.in | 7 gadi atpakaļ | |
| Makerules | 7 gadi atpakaļ | |
| README | 7 gadi atpakaļ | |
| Rules.mak | 7 gadi atpakaļ |
README
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 Alpha, ARC, ARM, Blackfin, CRIS, FR-V, HPPA,
IA64, LM32, M68K/Coldfire, Metag, Microblaze, MIPS, MIPS64, NDS32, NIOS2,
OpenRisc, PowerPC, SuperH, Sparc, x86, 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.
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-ng
disproportional to the added functionality.
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.LIB.
And most of all, be sure to have some fun! :-)
-Waldemar
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 Alpha, ARC, ARM, Blackfin, CRIS, FR-V, HPPA,
IA64, LM32, M68K/Coldfire, Metag, Microblaze, MIPS, MIPS64, NDS32, NIOS2,
OpenRisc, PowerPC, SuperH, Sparc, x86, 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.
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-ng
disproportional to the added functionality.
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.LIB.
And most of all, be sure to have some fun! :-)
-Waldemar