Ken Moffat wrote:
On Fri, Mar 18, 2016 at 04:54:45PM -0500, Bruce Dubbs wrote:
Trolltech has released qtwebkit-opensource-src-5.6.0.tar.xz.
(https://download.qt.io/community_releases/5.6/5.6.0/)
It is used for libprocessui from libksysguard (I don't think it is required)
in plasma and kf5 pim (which is not yet in the book)
The build instructions are really non standard. What I had to do was:
source setqt5
QT5PREFIX=$BUILDDIR/install
That sounds really weird - is BUILDDIR defined somewhere ?
Oh yes. Sorry. For me I usually use /tmp/packagname, but it really can
be anywhere there is space.
sed -i '/Werror/ s/isEqual/#isEqual/' \
Tools/qmake/mkspecs/features/unix/default_post.prf &&
syncqt.pl -version 5.6.0 Source/sync.profile &&
So, it ships a perl script that needs to be told what version it is
building ? That seems to be plain daft. Google suggests a version
of that script has been shipped for some time in qt, but we've never
had to know about it before.
Yes, I agree. I never heard of syncqt.pl before either. The comment in
the file says:
# Synchronizes Qt header files - internal development tool.
Tools/Scripts/build-webkit --prefix=$QT5PREFIX \
--qt \
--makeargs=-j4 \
--no-webkit2 &&
# test with 'Tools/Scripts/run-launcher'
sudo make -C WebKitBuild/Release install
It does not seem to support DESTDIR or equivalent.
Until now QT has always respected INSTALL_ROOT (with an underscore -
documented for qt4 in the wiki because I can never remember the
exact form). Did you try that ?
No, but a grep reveals that it is there. I'll try that.
When I built, it wanted
to delete things from my Qt5 directory, specifically /opt/qt5/include/
files, even though I told it to install in /tmp.
I suspect, in the absence of a DESTDIR-equivalent, it will only
install in /tmp if you use --prefix=/tmp.
I tried that. For $QT5PREFIX I used /tmp/qtwebkit
I did -makeargs=-j4 for timing purposes. If omitted, it uses all cores on
the system.
The "using all cores to build quicker, and then go idle" approach.
Thanks for noting how to override it.
Some statistics:
SBU: 18.2 (1689.8 seconds)
Tarball size: 33.667 MB
I think we can call that 34 ;)
Yes, I was just doing c&p.
Build Size: 837M
Install size: 163M (stripped)
The build/install log file is 44M
It appears to overwrite a lot of qt5 files. At least the timestamps have
been updated.
That is worrying - that was from a real install as root ?
Appeared to be that way but since I install in /opt/qt-5.6.0, I was able
to touch /opt/qt-5.6.0/xyz and then do 'find /opt/qt-5.6.0/ -newer
/opt/qt/xyz' and found only a few files installed. Actually too few. ldd
gave several 'not found' messages where I did find the missing libraries
in the build directory. I need to investigate the install more.
Dependencies:
Qt version 5.0.0 or later
gperf (v3.0 or later)
sqlite (development files)
fontconfig (development files)
xrender (development files)
phonon (development files)
libjpeg (development files)
libpng (development files)
Even with the --prefix above, it installs some files in the qt5 directory.
In my case libQt5WebKit.so.5.6.0 is installed in /opt/qt5/lib.
The bottom line is that --prefix is not really honored but the location of
qt5 is used for the actual libQt5WebKit.so library and supporting files.
Does it actually install anything in the prefix ?
Yes it did. Looked like a regular qt install -- just not the qtwebkit files.
Right now for Qt4 we include qtwebkit on the Qt4 page. I'm inclined to put
this on a separate page immediately below Qt5.
Comments?
For qt4, I do not like having qtwebkit on the same page, although
that is effectively dead now. For this one, your report that it
overwrites files from qt5 makes me wonder if we should indeed do it
all on one page. But I wonder how much it is needed : I suppose
that comes down to what the lxqt and qupzilla devs decide - I thought
qtwebkit was supposed to be going, but maybe I'm mistaken (googles
...) : looks as if QtWebEngine will be replacing it by 6.0, if I read
the entrails correctly. But 5.6 is supposed to be a first long term
support release of qt, so I suppose we will be stuck with qtwebkit for
years. I just hope it gets vulnerability fixes.
Yes, me too. For a presumed stable release, this seems to be quite marginal.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
