Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gettext-tiny: Add new package
Date: Tue, 21 Aug 2018 17:44:05 +0300	[thread overview]
Message-ID: <87pnybvky2.fsf@tkos.co.il> (raw)
In-Reply-To: <CACV=4zeWfsgbrQx4g2cmssEjtwvPj+a_9Fu5FzfSH4h_Q4fXdw@mail.gmail.com>

Hi Vadim,

Vadim Kochan writes:

> 2018-08-21 17:31 GMT+03:00 Baruch Siach <baruch@tkos.co.il>:
>> Vadim Kochan writes:
>>> From: Vadim Kochan <vadim.kochan@petcube.com>
>>> Add gettext-tiny package from the sabotage-linux project:
>>>
>>> gettext-tiny provides lightweight replacements for tools typically used
>>> from the GNU gettext suite, which is incredibly bloated and takes a lot
>>> of time to build (in the order of an hour on slow devices). the most
>>> notable component is msgfmt which is used to create binary translation
>>> files in the .mo format out of textual input files in .po format. this
>>> is the most important tool for building software from source, because it
>>> is used from the build processes of many software packages.
>>
>> Thanks. gettext is indeed a huge CPU cycles drain.
>>
>>> Signed-off-by: Vadim Kochan <vadim.kochan@petcube.com>
>>
>> [...]
>>
>>> +GETTEXT_TINY_VERSION = f733dd3fdd7be973f523a464165aae827a17d838
>>> +GETTEXT_TINY_SITE = $(call github,sabotage-linux,gettext-tiny,$(GETTEXT_TINY_VERSION))
>>> +GETTEXT_TINY_LICENSE = MIT
>>> +GETTEXT_TINY_INSTALL_STAGING = YES
>>> +GETTEXT_TINY_LICENSE_FILES = LICENSE
>>> +
>>> +ifeq ($(BR2_TOOLCHAIN_USES_MUSL),y)
>>> +LIBINTL=MUSL
>>> +endif
>>> +
>>> +ifeq ($(BR2_ENABLE_LOCALE),)
>>> +GETTEXT_TINY_DEPENDENCIES = libiconv
>>> +endif
>>> +
>>> +define GETTEXT_TINY_BUILD_CMDS
>>> +     $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) \
>>> +             LIBINTL=$(LIBINTL) \
>>> +             $(TARGET_CONFIGURE_OPTS)
>>> +endef
>>> +
>>> +define GETTEXT_TINY_INSTALL_STAGING_CMDS
>>> +     $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) \
>>> +             $(TARGET_CONFIGURE_OPTS) \
>>> +             DESTDIR=$(STAGING_DIR) prefix=/usr install
>>> +endef
>>> +
>>> +define GETTEXT_TINY_INSTALL_TARGET_CMDS
>>> +     $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) $(TARGET_CONFIGURE_OPTS) \
>>> +             DESTDIR=$(TARGET_DIR) prefix=/usr install
>>> +endef
>>> +
>>> +$(eval $(generic-package))
>>
>> What about a host package? Would it be feasible to replace host-gettext
>> with host-gettext-tiny?
>
> Well, I really do not know about usage it as host-getttext
> replacements (but I will try!),
> just add it for target only. Is it ok to let it go for the target only
> now and then
> check it if it can be used for the host mode ?

Of course. Adding a target gettext is perfectly fine as a first
step. Replacing host-gettext is a much bigger change, that can be done
later.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  parent reply	other threads:[~2018-08-21 14:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 14:22 [Buildroot] [PATCH 1/1] package/gettext-tiny: Add new package Vadim Kochan
2018-08-21 14:31 ` Baruch Siach
     [not found]   ` <CACV=4zeWfsgbrQx4g2cmssEjtwvPj+a_9Fu5FzfSH4h_Q4fXdw@mail.gmail.com>
2018-08-21 14:44     ` Baruch Siach [this message]
2018-08-21 15:29   ` Thomas Petazzoni
2018-08-21 15:51     ` Vadim Kochan
2018-08-21 17:36       ` Thomas Petazzoni
2018-08-21 20:07         ` Vadim Kochan
2018-08-21 20:10           ` Thomas Petazzoni
2018-08-22  7:02             ` Vadim Kochan
2018-10-09 12:45 ` Thomas Petazzoni
2018-10-09 13:12   ` Vadim Kochan
2018-10-09 13:12     ` Thomas Petazzoni

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=87pnybvky2.fsf@tkos.co.il \
    --to=baruch@tkos.co.il \
    --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