webkitgtk2 progress bar

webkitgtk2 progress bar

[Gary Thomas]

I see that the latest master update has brought a progress bar
for this (and presumably other 'cmake' based packages) - very nice :-)

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!)?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: webkitgtk2 progress bar

[Leonardo Sandoval]

On Wed, 2017-05-24 at 16:23 +0200, Gary Thomas wrote:
> I see that the latest master update has brought a progress bar
> for this (and presumably other 'cmake' based packages) - very nice :-)
> 
> 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!)?


this is not easy and from my side what I have done some profiling based
on the buildstats to figure out the top consumers recipes/tasks. As you
mentioned, webkitgtk is the winner, at least for utimes!

https://wiki.yoctoproject.org/wiki/MortyBuildstats
https://wiki.yoctoproject.org/wiki/TipsAndTricks/InvestigatingBuildTime

Leo



> 
> -- 
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------

Re: webkitgtk2 progress bar

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

You can try to use gold to save a bit of time linking the beast.

On Wed, May 24, 2017 at 4:46 PM, Leonardo Sandoval <
leonardo.sandoval.gonzalez@linux.intel.com> wrote:

> On Wed, 2017-05-24 at 16:23 +0200, Gary Thomas wrote:
> > I see that the latest master update has brought a progress bar
> > for this (and presumably other 'cmake' based packages) - very nice :-)
> >
> > 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!)?
>
>
> this is not easy and from my side what I have done some profiling based
> on the buildstats to figure out the top consumers recipes/tasks. As you
> mentioned, webkitgtk is the winner, at least for utimes!
>
> https://wiki.yoctoproject.org/wiki/MortyBuildstats
> https://wiki.yoctoproject.org/wiki/TipsAndTricks/InvestigatingBuildTime
>
> Leo
>
>
>
> >
> > --
> > ------------------------------------------------------------
> > Gary Thomas                 |  Consulting for the
> > MLB Associates              |    Embedded world
> > ------------------------------------------------------------
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 2239 bytes --]

Re: webkitgtk2 progress bar

[Alexander Kanavin]

On 05/24/2017 05:45 PM, Martin Jansa wrote:
> You can try to use gold to save a bit of time linking the beast.

webkit is already using gold by default, except for some architectures 
(aarch64, mips) where it used to fail - maybe it is not necessary anymore.

Alex

Re: webkitgtk2 progress bar

[Alexander Kanavin]

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

Re: webkitgtk2 progress bar

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

> 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@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@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 2942 bytes --]

Re: webkitgtk2 progress bar

[Trevor Woerner]

On Wed, May 24, 2017 at 1:16 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> 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.

...speaking of which...

It's probably about time someone sends a patch to remove cef, it has
been a while since anyone cared for it.

Re: webkitgtk2 progress bar

[Khem Raj]

On Wed, May 24, 2017 at 9:17 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> On Wed, May 24, 2017 at 1:16 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> 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.
>
> ...speaking of which...
>
> It's probably about time someone sends a patch to remove cef, it has
> been a while since anyone cared for it.

yes please remove it. I was the one who was probably most interested
in it in past.