Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
...I will have a look at my webengine build again (it takes about 15 hours to build!...
Try rebuilding just QtWebEngine by itself enabling the proprietary codecs. It shouldn't take nearly that long to build. And I guess Falkon may need rebuilding, but that doesn't take long.
P.S.: I'm using an oldish Pentium Dual-Core E6500 processor and 8GB RAM. For me, without specifying a parallel make, QtWebEngine by itself takes 5 hours to compile making it the longest-building thing I use. QupZilla takes 15 minutes. So deciding to install QupZilla is no small thing, but it is a nice browser. I installed QupZilla-2.2.6 which is probably the last version that will be released. Maybe later I will work on replacing QupZilla with its KDE variant Falkon. That is probably where the idea of QupZilla will continue on and be perfected.
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,150
Rep:
qtwebengine wont build with the git version of ffmpeg, I use ffmpeg a LOT so I prefer the latest version, trying again without the ffmpeg flag, but it does take a LLLOOOOoooooooNNNNNnnnnggggg time on my machine, one day I'll check my SBU's!
P.S.
qtweb engine was already built with the proprietary-codecs flags anyway, but we will see what happens.
Of course I am only rebuilding webengine not all of qt5!
Last edited by Keith Hedger; 08-16-2018 at 06:10 AM.
I couldn't build QtWebEngine with my system ICU. According to build help, QtWebEngine can treat ffmpeg that way. Maybe you can install your preferred version of ffmpeg for the system, and configure QtWebEngine to use the qt internal version. The browser probably will work perfectly well, and you can still have a cutting edge ffmpeg on the system.
P.S.: A while back I bought an off-lease Lenovo Thinkcentre with an Intel Core 2 Duo processor for $99 and free shipping from Newegg. I've bought a lot of used computers over the years, and this turned out to be cleanest used machine of them all. It's a small thing that I keep in a spare bedroom. I use it to run my build scripts that sometimes can run for 24 hours straight. Then I clone the final system to other computers that I use. So I don't really like things that take forever to build like LLVM, LibreOffice, Qt, QtWebEngine, etc., but for $99 I can push that stuff into the background and go mow the lawn or something.
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,150
Rep:
H.264 doesn't show/play, webm and ogg theora play Ok.
I'm wondering if originally I had installed webengine before installing x264, I'll find out after it finishes building again!.
Built fine with my system ICU, leastways it didn't complain or fall over.
I tend to build libreoffice/qt and other big builds overnight, can't really afford a new machine at the moment
And it now plays the h.264 video from your link, thanks Stoat!
Can't find the dictionary so I will fix that next.
OK fixed the dictionary now, it was just in the wrong place.
Last edited by Keith Hedger; 08-16-2018 at 10:43 AM.
Reason: xtra ino
I managed to get Falkon installed without having KDE installed. It required only one of the KDE Framework packages (ki18n). It warned about not finding four optionals. One of those was KF5Wallet for passwords (which I never store in any browser), and the other three were "experimental" Python plugins (PySide2, Shiboken2, PythonLibs).
Falkon looks good and works, but some buttons are invisible until the mouse rolls over them (menu, tools, home, refresh, back). And it tries to load the Linux theme on startup but can't. In fact, there are no themes at all listed to choose from in Preferences>Appearance. In QupZilla the themes are installed in /usr/share/qupzilla, but Falkon appears not to have installed any of them anywhere.
I wonder if the themes issue is causing the buttons thing. And I wonder if that existing installation of QupZilla caused Falkon not to install the themes folders. And I wonder if those Python plugins are not-so-optional after all. BTW this is all being done on a cloned system for testing.
Anyway is your Falkon build is doing any of these things, or is it behaving and looking like QupZilla (which I guess it should)?
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,150
Rep:
Not had those problems,what version of ki18n have you installed as the one in BLFS sbn is not available I used ki18n-5.49.0 which is required, I remember the warning about kwallet but not the python stuff.
I did a quick staged install to /tmp just to make sure every thing was right, and not every thing got installed then I tried a full install with this tarball
Thanks for all that. It helped. I have Falkon working and looking properly now. On the first try I used the super-simple steps in the README file, and everything (including those themes) went to /usr/local. It still should have been okay, but it wasn't this time for some reason or another.
The missing themes WERE the cause of the invisible buttons. Those are all fixed now.
Some of your cmake options are rejected or ignored. See all that at the end of the output of your cmake command. See the list of valid options and their defaults by running cmake -LH in the build directory.
And finally, I found the older ki18n file version used by the KDE Frameworks version in BLFS-8.2 in https://download.kde.org/Attic/. It's two directory levels up from the repo used by the book.
Onward now with Falkon. I liked QupZilla the way it was. Now I'm expecting it to advance and improve as Falkon. Everybody who can tolerate building QtWebEngine should give it a try. For me, it's easily worth the effort.
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,150
Rep:
Glad to help.I use a set of standard options to cmake/qmake some of the cmake files ignore some options some don't some fall over, not really a lover of the whole cmake system, much prefer a proper configure.
If you use a mix of gtk and qt you may want to take a look at qt5ct if you havn't already, here:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
