2009-09-20 00:03:24 +02:00
|
|
|
{ stdenv, fetchurl, libiconv }:
|
2009-04-22 01:18:09 +02:00
|
|
|
|
2009-09-19 14:21:39 +02:00
|
|
|
stdenv.mkDerivation (rec {
|
2010-05-10 14:33:43 +02:00
|
|
|
name = "gettext-0.18";
|
2009-04-22 01:18:09 +02:00
|
|
|
|
2008-02-22 04:06:12 +01:00
|
|
|
src = fetchurl {
|
|
|
|
url = "mirror://gnu/gettext/${name}.tar.gz";
|
2010-05-10 14:33:43 +02:00
|
|
|
sha256 = "1rbgm6sxgq218pridn2vji5nlj3hdf4vs75rz00wc0wcw4fjqd02";
|
2008-02-22 04:06:12 +01:00
|
|
|
};
|
2009-09-19 13:04:33 +02:00
|
|
|
|
2009-04-22 01:18:09 +02:00
|
|
|
configureFlags = "--disable-csharp";
|
2009-09-19 13:04:33 +02:00
|
|
|
|
2009-11-23 20:38:34 +01:00
|
|
|
# On cross building, gettext supposes that the wchar.h from libc
|
|
|
|
# does not fulfill gettext needs, so it tries to work with its
|
|
|
|
# own wchar.h file, which does not cope well with the system's
|
|
|
|
# wchar.h and stddef.h (gcc-4.3 - glibc-2.9)
|
|
|
|
preConfigure = ''
|
|
|
|
if test -n "$crossConfig"; then
|
|
|
|
echo gl_cv_func_wcwidth_works=yes > cachefile
|
|
|
|
configureFlags="$configureFlags --cache-file=`pwd`/cachefile"
|
|
|
|
fi
|
|
|
|
'';
|
|
|
|
|
2010-03-09 19:05:38 +01:00
|
|
|
crossAttrs = {
|
|
|
|
buildInputs = stdenv.lib.optional (stdenv.gccCross.libc ? libiconv)
|
|
|
|
stdenv.gccCross.libc.libiconv.hostDrv;
|
|
|
|
};
|
|
|
|
|
2009-09-19 13:04:33 +02:00
|
|
|
meta = {
|
|
|
|
description = "GNU gettext, a well integrated set of translation tools and documentation";
|
|
|
|
|
|
|
|
longDescription = ''
|
|
|
|
Usually, programs are written and documented in English, and use
|
|
|
|
English at execution time for interacting with users. Using a common
|
|
|
|
language is quite handy for communication between developers,
|
|
|
|
maintainers and users from all countries. On the other hand, most
|
|
|
|
people are less comfortable with English than with their own native
|
|
|
|
language, and would rather be using their mother tongue for day to
|
|
|
|
day's work, as far as possible. Many would simply love seeing their
|
|
|
|
computer screen showing a lot less of English, and far more of their
|
|
|
|
own language.
|
|
|
|
|
|
|
|
GNU `gettext' is an important step for the GNU Translation Project, as
|
|
|
|
it is an asset on which we may build many other steps. This package
|
|
|
|
offers to programmers, translators, and even users, a well integrated
|
|
|
|
set of tools and documentation. Specifically, the GNU `gettext'
|
|
|
|
utilities are a set of tools that provides a framework to help other
|
|
|
|
GNU packages produce multi-lingual messages.
|
|
|
|
'';
|
|
|
|
|
|
|
|
homepage = http://www.gnu.org/software/gettext/;
|
|
|
|
|
|
|
|
maintainers = [ stdenv.lib.maintainers.ludo ];
|
2010-05-10 14:33:43 +02:00
|
|
|
platforms = stdenv.lib.platforms.all;
|
2009-09-19 13:04:33 +02:00
|
|
|
};
|
2008-02-22 04:06:12 +01:00
|
|
|
}
|
2009-09-19 13:04:33 +02:00
|
|
|
|
|
|
|
//
|
|
|
|
|
2009-10-13 12:03:44 +02:00
|
|
|
(if (!stdenv.isLinux) # any non-GNU system
|
2009-09-19 14:21:39 +02:00
|
|
|
then {
|
2009-09-20 00:03:24 +02:00
|
|
|
buildInputs = [ libiconv ];
|
2009-09-19 14:21:39 +02:00
|
|
|
}
|
|
|
|
else {}))
|