-GNULib is intended to be the canonical source for most of the important
-"Portability" files for GNU projects.
+Gnulib is intended to be the canonical source for most of the important
+"portability" and/or common files for GNU projects. These are files
+intended to be shared at the source level; Gnulib is not a library meant
+to be installed and linked against.
-While portability is not one of our primary goals, it has helped
-introduce many people to the GNU system, and is worthwhile when it can
-be achieved at a low cost. This collection helps lower that cost.
+While portability across operating systems is not one of GNU's primary
+goals, it has helped introduce many people to the GNU system, and is
+worthwhile when it can be achieved at a low cost. This collection helps
+lower that cost.
-gpl/ - Any source files licensed under the GNU General Public License
-lgpl/ - Any source files licensed under the GNU Lesser GPL
-doc/ - Any documents that may be nice to have in applications. This
-includes such files as 'COPYING, COPYING.LIB, etc.'
-
-Contributing to GNULib
All software here is Copyright (c) Free Software Foundation - you need
to have filled out an assignment form for a project that uses the
module for that contribution to be accepted here.
If you have a piece of code that you would like to contribute, please
All software here is Copyright (c) Free Software Foundation - you need
to have filled out an assignment form for a project that uses the
module for that contribution to be accepted here.
If you have a piece of code that you would like to contribute, please
-email bug-gnulib@gnu.org. We will add you to the maintainers list.
+email bug-gnulib@gnu.org. You can review the archives, subscribe, etc.,
+via http://lists.gnu.org/mailman/listinfo/bug-gnulib.
If your functions define completely new but rarely used functionality,
you should probably consider packaging it as a separate library.
If your functions define completely new but rarely used functionality,
you should probably consider packaging it as a separate library.
-
-GNULib contains code both under GPL and LGPL. Because several packages
-that use GNULib are GPL, the files state they are licensed under GPL.
+Gnulib contains code both under GPL and LGPL. Because several packages
+that use Gnulib are GPL, the files state they are licensed under GPL.
However, to support LGPL projects as well, you may use some of the
files under LGPL. The "License:" information in the files under
modules/ clarifies the real license that applies to the module source.
However, to support LGPL projects as well, you may use some of the
files under LGPL. The "License:" information in the files under
modules/ clarifies the real license that applies to the module source.
license them under a compatible license, which means that sometimes
the contribution will have to be LGPL, if the original file is
available under LGPL via a "License: LGPL" information in the
projects' modules/ file.
license them under a compatible license, which means that sometimes
the contribution will have to be LGPL, if the original file is
available under LGPL via a "License: LGPL" information in the
projects' modules/ file.
* Add the header files and source files to lib/.
* If the module needs configure-time checks, write an autoconf
macro for it in m4/<module>.m4. See m4/README for details.
* Add the header files and source files to lib/.
* If the module needs configure-time checks, write an autoconf
macro for it in m4/<module>.m4. See m4/README for details.
undesirable variability in implementations. For example, an
application that uses the 'malloc' module need not worry about (malloc
(0)) returning NULL on some Standard C platforms; and 'time_r' users
need not worry about localtime_r returning int (not char *) on some
platforms that predate POSIX 1003.1-2001.
undesirable variability in implementations. For example, an
application that uses the 'malloc' module need not worry about (malloc
(0)) returning NULL on some Standard C platforms; and 'time_r' users
need not worry about localtime_r returning int (not char *) on some
platforms that predate POSIX 1003.1-2001.
4.2BSD, but it is a maintenance hassle to maintain compatibility with
unused hosts, so currently we assume at least a freestanding C89
compiler, possibly operating with a C library that predates C89. The
4.2BSD, but it is a maintenance hassle to maintain compatibility with
unused hosts, so currently we assume at least a freestanding C89
compiler, possibly operating with a C library that predates C89. The
on 1998-09-30, and Sun dropped support for it on 2003-10-01, so at
some point we may start assuming a C89 library as well.
on 1998-09-30, and Sun dropped support for it on 2003-10-01, so at
some point we may start assuming a C89 library as well.
<float.h>, <limits.h>, <stdarg.h>, and <stddef.h> unconditionally. It
can also include hosted headers like <errno.h> that were present in
Unix Version 7 and are thus widely available. Similarly, many modules
<float.h>, <limits.h>, <stdarg.h>, and <stddef.h> unconditionally. It
can also include hosted headers like <errno.h> that were present in
Unix Version 7 and are thus widely available. Similarly, many modules
since <sys/types.h> has been around nearly forever. <string.h> and
<stdlib.h> were not in Unix Version 7, so they weren't universally
available on ancient hosts, but they are both in SunOS 4 (the oldest
since <sys/types.h> has been around nearly forever. <string.h> and
<stdlib.h> were not in Unix Version 7, so they weren't universally
available on ancient hosts, but they are both in SunOS 4 (the oldest
Even if the include files exist, they may not conform to C89.
However, GCC has a "fixincludes" script that attempts to fix most
Even if the include files exist, they may not conform to C89.
However, GCC has a "fixincludes" script that attempts to fix most
largely conform to C89 or better. People still using ancient hosts
should use fixincludes or fix their include files manually.
Even if the include files conform to C89, the library itself may not.
largely conform to C89 or better. People still using ancient hosts
should use fixincludes or fix their include files manually.
Even if the include files conform to C89, the library itself may not.
must avoid freeing a null pointer, even though C89 allows it.
You can work around some of these problems by requiring the relevant
must avoid freeing a null pointer, even though C89 allows it.
You can work around some of these problems by requiring the relevant
code can assume that standard internal types like size_t are no wider
than 'long'. POSIX 1003.1-2001 and the GNU coding standards both
code can assume that standard internal types like size_t are no wider
than 'long'. POSIX 1003.1-2001 and the GNU coding standards both
-require 'int' to be at least 32 bits wide, so GNULib code assumes this
-as well. GNULib code makes the following additional assumptions:
+require 'int' to be at least 32 bits wide, so Gnulib code assumes this
+as well. Gnulib code makes the following additional assumptions:
* Signed integer arithmetic is two's complement, without runtime
overflow checking. This is the traditional behavior, and is
* Signed integer arithmetic is two's complement, without runtime
overflow checking. This is the traditional behavior, and is
following should work:
$ cvs -d :pserver:anoncvs@cvs.gnu.org:/cvsroot/gnulib login
(Just hit Enter or Return when prompt for a password)
$ cvs -d :pserver:anoncvs@cvs.gnu.org:/cvsroot/gnulib checkout gnulib
following should work:
$ cvs -d :pserver:anoncvs@cvs.gnu.org:/cvsroot/gnulib login
(Just hit Enter or Return when prompt for a password)
$ cvs -d :pserver:anoncvs@cvs.gnu.org:/cvsroot/gnulib checkout gnulib
-Copyright (C) 2001, 2003, 2004 Free Software Foundation, Inc.
+-----
+Copyright (C) 2001, 2003, 2004, 2005 Free Software Foundation, Inc.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by