From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-04-15
Date: Tue, 16 Apr 2019 22:31:15 +0200 [thread overview]
Message-ID: <20190416223115.1c314a13@windsurf> (raw)
In-Reply-To: <f6c8d29f-eb44-6b16-a94b-a09186c47c2b@micronovasrl.com>
Hello,
On Tue, 16 Apr 2019 17:18:54 +0200
Giulio Benetti <giulio.benetti@micronovasrl.com> wrote:
> So, if I don't understand wrong, when BR2_SYSTEM_ENABLE_NLS is disabled
> we want all packages not to produce translation files.
Ideally yes.
> Then if a package tries anyway to produce translation files we need to
> fix it by checking BR2_SYSTEM_ENABLE_NLS(depends on
> !BR2_SYSTEM_ENABLE_NLS etc.) in its Config.in file.
I guess you wanted to say "if a package tries anyway to produce
translation files, we need to fix it by adding a depends on
BR2_SYSTEM_ENABLE_NLS". If that's what you meant, then I believe the
answer is no.
gettext-tiny provides some dummy implementation of the gettext tools,
so we can use these if a package really wants to generate translation
files despite BR2_SYSTEM_ENABLE_NLS being disabled. However, if there's
a reasonable way to tell the package to not generate translation files,
I'd say we should prefer that.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-16 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-04-15 Thomas Petazzoni
2019-04-16 9:47 ` Vadym Kochan
2019-04-16 9:53 ` Vadym Kochan
2019-04-16 10:24 ` Giulio Benetti
2019-04-16 11:44 ` Thomas Petazzoni
2019-04-16 15:18 ` Giulio Benetti
2019-04-16 20:31 ` Thomas Petazzoni [this message]
2019-04-17 9:28 ` Giulio Benetti
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=20190416223115.1c314a13@windsurf \
--to=thomas.petazzoni@bootlin.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