From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libgpg-error: optionally depends on gettext
Date: Thu, 25 Aug 2016 10:33:27 +0200 [thread overview]
Message-ID: <20160825103327.148da292@free-electrons.com> (raw)
In-Reply-To: <20160824231003.29262-1-arnout@mind.be>
Hello,
On Thu, 25 Aug 2016 01:10:02 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> +ifeq ($(BR2_NEEDS_GETTEXT),y)
> +LIBGPG_ERROR_DEPENDENCIES += gettext
> +endif
If you add gettext as a dependency, then the Config.in should be adjust
accordingly, otherwise the mechanism that checks when a package gets
built that it is really selected in the configuration will abort the
build.
The manual at
https://buildroot.org/downloads/manual/manual.html#_gettext_integration_and_interaction_with_packages
has some details on the gettext interaction:
"""
Packages that need gettext only when locale support is enabled should:
- use select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT_IF_LOCALE in
the Config.in file;
- use $(if $(BR2_NEEDS_GETTEXT_IF_LOCALE),gettext) in the package
DEPENDENCIES variable in the .mk file.
Packages that unconditionally need gettext (which should be very rare)
should:
- use select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT in the
Config.in file;
- use $(if $(BR2_NEEDS_GETTEXT),gettext) in the package
DEPENDENCIES variable in the .mk file.
"""
Then I believe there's possibly a *third* case, which the manual
doesn't describe, but that we should document: packages that *may* use
gettext if available, but which can work without it. In this case:
ifeq ($(BR2_PACKAGE_GETTEXT),y)
<pkg>_DEPENDENCIES += gettext
endif
would be the correct solution.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-08-25 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 23:10 [Buildroot] [PATCH 1/2] package/libgpg-error: optionally depends on gettext Arnout Vandecappelle
2016-08-24 23:10 ` [Buildroot] [PATCH 2/2] package/iputils: link with -lintl Arnout Vandecappelle
2016-08-25 3:51 ` Baruch Siach
2016-08-25 8:18 ` Thomas Petazzoni
2016-08-25 8:56 ` Arnout Vandecappelle
2016-08-25 8:57 ` Arnout Vandecappelle
2016-08-25 13:07 ` Thomas Petazzoni
2016-08-25 13:17 ` Arnout Vandecappelle
2016-08-25 13:37 ` Thomas Petazzoni
2016-08-25 14:39 ` Arnout Vandecappelle
2016-08-25 8:33 ` Thomas Petazzoni [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=20160825103327.148da292@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox