From: Vadim Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/wine: Add gettext dependency for host-wine only with NLS enabled
Date: Sat, 5 Jan 2019 22:00:44 +0200 [thread overview]
Message-ID: <20190105200046.31512-2-vadim4j@gmail.com> (raw)
In-Reply-To: <20190105200046.31512-1-vadim4j@gmail.com>
Checked that host-wine compiles ok without host-gettext, so no
needs to specify this dependency.
libgettextpo is required by tools/wrc (https://linux.die.net/man/1/wrc)
which allows to convert windows resources also to *.po format, which is
not needed if NLS is disabled.
Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
---
package/wine/wine.mk | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/wine/wine.mk b/package/wine/wine.mk
index 78c8e6ab63..7e44e3c81d 100644
--- a/package/wine/wine.mk
+++ b/package/wine/wine.mk
@@ -307,8 +307,12 @@ WINE_CONF_OPTS += --without-zlib
endif
# host-gettext is essential for .po file support in host-wine wrc
+ifeq ($(BR2_SYSTEM_ENABLE_NLS),y)
HOST_WINE_DEPENDENCIES += host-gettext
HOST_WINE_CONF_OPTS += --with-gettext --with-gettextpo
+else
+HOST_WINE_CONF_OPTS += --without-gettext --without-gettextpo
+endif
# Wine needs to enable 64-bit build tools on 64-bit host
ifeq ($(HOSTARCH),x86_64)
--
2.14.1
next prev parent reply other threads:[~2019-01-05 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 20:00 [Buildroot] [PATCH v2 0/3] Add gettext-tiny package Vadim Kochan
2019-01-05 20:00 ` Vadim Kochan [this message]
2019-02-06 13:12 ` [Buildroot] [PATCH v2 1/3] package/wine: Add gettext dependency for host-wine only with NLS enabled Thomas Petazzoni
2019-01-05 20:00 ` [Buildroot] [PATCH v2 2/3] package/gettext: Turn into virtual package Vadim Kochan
2019-01-05 20:00 ` [Buildroot] [PATCH v2 3/3] package/gettext-tiny: Add new package Vadim Kochan
2019-01-13 19:50 ` Vadim Kochan
2019-01-30 12:03 ` [Buildroot] [PATCH v2 0/3] Add gettext-tiny package Vadym Kochan
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=20190105200046.31512-2-vadim4j@gmail.com \
--to=vadim4j@gmail.com \
--cc=buildroot@busybox.net \
/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.