On Wed, Jul 15, 2015 at 12:27:38AM +0200, Armin K. wrote:
> On 15.07.2015 00:16, Ken Moffat wrote:
> > When I first built qt5, a few months ago, I used it to build
> > qupzilla as my backup browser.  And that needed whatever the web
> > part was called at that time.  So yes, I know how long the "reduced"
> > and "with the web thingy" builds take (I'm not sure if webengine is
> > the same thing that was in that older version).
> > 
> 
> I suppose you are talking about QtWebKit. Yes, that's still part of
> Qt5, but it's soon going away in favor of QtWebEngine.
> 
Yes, that was it!  I'm really not very good at this [ deliberately
echoing the captain of the B Ark in hhg2tg ]

> QtWebKit and QtWebEngine are not one and the same - they are different
> components which seem to do similar thing, just in a different way.
>

So that version would not, in any case, have been useful to me for
qupzilla.  I stand corrected.

> QtWebKit is a port of WebKit browser engine to Qt platform while
> QtWebEngine is port of Chromium's/Chrome's browser engine (Blink,
> which is itself a fork of WebKit) to the Qt platform.
> 

So, I'll blame google for the build failure (I could not possibly
blame the gcc devs ;)

I left the attempt to compile qt with 4.2.0-rc2 while I had
something to eat - I'm sure it will still be compiling when I get
back to it, even if it is now using all the processors.

ĸen
-- 
This one goes up to eleven!
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to