[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Making libunistring optional
From: |
Ludovic Courtès |
Subject: |
Making libunistring optional |
Date: |
Sat, 17 Nov 2012 23:21:24 +0100 |
User-agent: |
Gnus/5.130005 (Ma Gnus v0.5) Emacs/24.2 (gnu/linux) |
Hello,
Here’s an attempt to “reduce the number of dependencies” of Guile. The
approach, as suggested by Bruno Haible, uses Gnulib’s
‘libunistring-optional’ module, along with the 22 (!) unistring modules
that provide the functionality we need.
When libunistring is available, it is used as before; when it’s not,
those modules are built and linked into libguile.
I had become convinced that this is a good idea, and a simple way to
make our user’s lives easier. Yet, this adds 184 source files to the
tarball (would be more if we included tests), so I’d like to hear
opinions.
Thoughts?
Ludo’.
0001-Use-Gnulib-s-libunistring-optional-and-22-unistring-.patch.gz
Description: the patch
- Making libunistring optional,
Ludovic Courtès <=