gnulib - GNU portability library - Summary
This software is part of the GNU Project.
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 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.
There is no distribution tarball; developers should just grab source files from the repository. Please see <http://www.gnu.org/software/gnulib/> for more details.
Registration Date: Wed 17 Oct 2001 05:49:50 PM UTC
License: GNU General Public License v2 or later
Development Status: 5 - Production/Stable
posted by haible, Fri 26 Apr 2024 10:12:40 AM UTC
If you are developer on a package that uses GNU gnulib as part of its build system:
gnulib-tool has been known for being slow for many years. We have listened to your complaints. We have rewritten gnulib-tool in another programming language (Python). It is between 8 times and 100 times faster than the previous implementation.
[...]
posted by haible, Sun 21 Apr 2024 10:47:35 AM UTC
If you are developer on a package that uses GNU gnulib as part of its build system:
gnulib-tool has been known for being slow for many years. We have listened to your complaints. A rewrite of gnulib-tool in another programming language (Python) is ready for beta-testing. It is between 8 times and 100 times faster than the original gnulib-tool.
[...]
posted by haible, Sat 15 Apr 2023 10:31:06 PM UTC
An Android app has a UI written in Java, not on top of a C/C++ based GUI toolkit (GNOME, Qt, KDE, wxWidgets, ...). Gnulib cannot help you porting this part of an application to Android.
But when an application has a large part written in C, and you want to reuse this part in the Android app, Gnulib is useful. Recently, Android has been added to
[...]
posted by haible, Sun 20 Nov 2022 04:27:43 PM UTC
Spawning a new process has traditionally been coded by a fork() call, followed by an execv/execl/execlp/execvp call in the child process. This is often referred to as the fork + exec idiom.
In 90% of the cases, there is something better: the posix_spawn/posix_spawnp functions.
[...]
Powered by Savane 3.13-7f26.
Corresponding source code