From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/libtextstyle: new package
Date: Mon, 23 Mar 2020 18:33:27 +0100 [thread overview]
Message-ID: <20200323173327.GH22325@scaer> (raw)
In-Reply-To: <20200314152512.708b5d06@windsurf>
Thomas, All,
On 2020-03-14 15:25 +0100, Thomas Petazzoni spake thusly:
> On Thu, 12 Mar 2020 13:10:01 -0700
> aduskett at gmail.com wrote:
>
> > From: Adam Duskett <Aduskett@gmail.com>
> >
> > This library provides an easy way to add styling to programs that produce
> > output to a console or terminal emulator window.
> >
> > libtextstyle is for you if your application produces text that is more readable
> > when it is accompanied with styling information, such as color, font attributes
> > (weight, posture), or underlining.
> >
> > Newer versions of gettext-gnu require this package.
> >
> > Tested with test-pkg -p gettext-tiny in Debian 10 and Centos 7
> >
> > br-arm-full [1/6]: OK
> > br-arm-cortex-a9-glibc [2/6]: OK
> > br-arm-cortex-m4-full [3/6]: OK
> > br-x86-64-musl [4/6]: OK
> > br-arm-full-static [5/6]: OK
> > sourcery-arm [6/6]: OK
> >
> > Signed-off-by: Adam Duskett <Aduskett@gmail.com>
>
> I'm confused. Why do we need a separate for this, if this is part of
> gettext-gnu, and needed only by gettext-gnu ?
So, for the records, in cae you missed the IRC discussion:
- our gettext-gnu package has: HOST_GETTEXT_GNU_SUBDIR = gettext-tools
so only the gettext-tools sub-directory is configured and built
- gettext-tools need libtextstyle, but that is not getting configured
nor built
So we have three options:
- add hooks to configure + build libtextstyles as a pre-configure hook
in gettext-gnu, and install it in a pre-install hook,
- add a separate package for libtextstyle,
- revert to building the whole of gettext.
Adam did some timings with BR2_JLEVEL=4, and he got:
- just getext-tools: 38.86s user 22.13s system 124% cpu 49.035 total
- just libtextstyles: 40.78s user 14.57s system 146% cpu 37.817 total
- whole of gettext: 203.18s user 122.87s system 161% cpu 3:22.39 total
So, the whole of gettext is still ~4x the time to build the tools and
libtextstyle. This is not acceptable...
I think hacking the build of libtextstyles with hooks is not gonna fly
far either.
So we're back at a separate package as the only viable solution, I'm
afraid.
Does that make sense?
Of course, we need to write that down in a commit log somewhere... ;-)
Regards,
Yann E. MORIN.
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2020-03-23 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 20:10 [Buildroot] [PATCH v2 1/3] package/libtextstyle: new package aduskett at gmail.com
2020-03-12 20:10 ` [Buildroot] [PATCH v2 2/3] package/gettext-gnu: bump version to 0.20.1 aduskett at gmail.com
2020-03-30 17:57 ` Bernd Kuhls
2020-03-12 20:10 ` [Buildroot] [PATCH v2 3/3] package/gettext-tiny: support gettext 0.20.1 aduskett at gmail.com
2020-03-12 23:57 ` [Buildroot] [PATCH v2 1/3] package/libtextstyle: new package vadim4j at gmail.com
2020-03-14 14:25 ` Thomas Petazzoni
2020-03-23 17:33 ` Yann E. MORIN [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=20200323173327.GH22325@scaer \
--to=yann.morin.1998@free.fr \
--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