From: Johannes Sixt <j6t@kdbg.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Do not build i18n on Windows.
Date: Sat, 14 Aug 2010 10:24:41 +0200 [thread overview]
Message-ID: <201008141024.42093.j6t@kdbg.org> (raw)
In-Reply-To: <AANLkTiku5R+idX-C8f0AcCikBLmfEb5ZEhdft+CSRzU0@mail.gmail.com>
On Samstag, 14. August 2010, Ævar Arnfjörð Bjarmason wrote:
> On Fri, Aug 13, 2010 at 22:02, Johannes Sixt <j6t@kdbg.org> wrote:
> > We do not have the necessary libraries and tools.
>
> Just curious, do you mean Windows / MINGW can't build gettext, or that
> you just haven't done so in your build process yet? At least
> http://www.mingw.org/wiki/LibrariesAndTools seems to indicate that
> libintl has been ported to Windows.
The msysgit build environment that I am using does not have libintl. The
reason *might* be that I haven't updated it since months. Upstream msysgit
could already have it.
The MSVC build environment doesn't have libintl in any case. Even if msysgit
gains libintl, the MSVC does *not* automatically gain it as well. Hence,
setting NO_GETTEXT in the MSVC section of the Makefile makes sense for now.
BTW, libintl is not the only obstacle: the gettext tools are needed as well.
> If you're just not interested in building gettext by default on
> Windows I think it's completely reasonable to add it to the Makefile
> (given that you're probably pretty much the only one doing so). It
> would just be useful to clarify the "why".
As long as libintl and the gettext tools are not in msysgit, we should set
NO_GETTEXT for MinGW builds. Once we have them, I don't care that much
whether we set it by default or not.
-- Hannes
prev parent reply other threads:[~2010-08-14 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 22:02 [PATCH] Do not build i18n on Windows Johannes Sixt
2010-08-13 22:19 ` Ævar Arnfjörð Bjarmason
2010-08-14 8:24 ` Johannes Sixt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201008141024.42093.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.