[yocto] webkitgtk2 progress bar

[Martin Jansa]

> I have 22 cores here, and it is not a luxury, but an absolute necessity
to get anything done as far as oe-core maintenance goes. Webkit's
do_compile takes about half an hour - I can almost see that progress bar
move :)

Heh, you're lucky with "oe-core maintenance".

My "bitbake world" builds have few components like this, webkitgtk (used to
have webkit1, webkit2 and webkit2-efl as separate builds), 2 chromiums (x11
and wayland), cef (luckily broken and whitelisted for a while), firefox,
qtwebengine, qtwebkit. Each taking usually even more time than "simplest"
webkitgtk2.

Building world with just oe-core takes just hour(s), add few layers like me
and it's day(s).

So progress bars are nice, but I still hate looking at them.

On Wed, May 24, 2017 at 6:43 PM, Alexander Kanavin <
alexander.kanavin at linux.intel.com> wrote:

> On 05/24/2017 05:23 PM, Gary Thomas wrote:
>
>> Now [tongue-in-cheek], can someone do something about the horrendous
>> build times for such packages (webkitgtk2 can take up to 3 hours on
>> my [no so slow] build host!)?
>>
>
> In order of decreasing tongue in cheekiness.
>
> 1. Rewrite webkit in something that is not C++ - by far the most awful
> language when it comes to compile times.
>
> 2. Use icecc.bbclass to 'borrow' computing power from colleagues
> (untested, unproven).
>
> 3. Invest into a serious CPU. I have 22 cores here, and it is not a
> luxury, but an absolute necessity to get anything done as far as oe-core
> maintenance goes. Webkit's do_compile takes about half an hour - I can
> almost see that progress bar move :)
>
> Alex
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170524/8e1ddee6/attachment.html>