bug-gettext
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] replacing autotools with meson?


From: Alexander Kanavin
Subject: Re: [bug-gettext] replacing autotools with meson?
Date: Thu, 17 Aug 2017 16:25:35 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

On 08/16/2017 07:34 PM, Bruno Haible wrote:
Alexander Kanavin wrote:
Yocto is not a distribution, and it does not provide any pre-built
binaries or images. It is a toolkit for creating Linux-based
distributions aimed at embedded use cases. What this means is that
anyone who wants to create such a distribution and produce images and
packages that can be placed on their target devices needs to configure
exactly what gets built and how, and then perform the build on their
development machine iteratively, until they are happy with the outcome.
So we aggressively parallelize and cache everything: when multiple
software packages can be built at the same time, they are. Build
artifacts are placed into a disk cache, and reused whenever possible.

I see. Thanks for explaining.

Now, as mentioned in the other mail, try to see gettext as the union of
gettext-runtime and gettext-tools. You can configure, "make", "make install"
each of these subdirectories separately.

Thanks. We indeed treat gettext as a monolith that is fully built in a single (long) step; I can first try to see where and how pieces of it are getting used, and split up the build accordingly.


Alex



reply via email to

[Prev in Thread] Current Thread [Next in Thread]