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. Our gettext-gnu package currently has HOST_GETTEXT_GNU_SUBDIR = gettext-tools so we only configure and build the gettext-tools sub-directory. Version 0.20.1 of gettext-gnu now requires libtextstyle, which the subdirectory gettext-tools does not provide. We have three options: 1) Add hooks to configure and build libtextstyle as a pre-configure hook in gettext-gnu, and install it in a pre-install hook. 2) Revert to building the whole of gettext. 3) Add a separate package for libtextstyle. Here are the results of a test with BR2_JLEVEL=4: - Only gettext-tools: 38.86s user 22.13s system 124% CPU 49.035 total - gettext + libtextstyle: 40.78s user 14.57s system 146% CPU 37.817 total - All of gettext: 203.18s user 122.87s system 161% CPU 3:22.39 total As seen above, compiling the entire gettext package takes 5x longer than building libtextstyle and gettext separately! As such, the best option is option 3, as the time increase to build libtextstyle is negligible. 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> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
---|---|---|
arch | ||
board | ||
boot | ||
configs | ||
docs | ||
fs | ||
linux | ||
package | ||
support | ||
system | ||
toolchain | ||
utils | ||
.defconfig | ||
.flake8 | ||
.gitignore | ||
.gitlab-ci.yml | ||
.gitlab-ci.yml.in | ||
CHANGES | ||
Config.in | ||
Config.in.legacy | ||
COPYING | ||
DEVELOPERS | ||
Makefile | ||
Makefile.legacy | ||
README |
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on Freenode IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches