View Single Post
Old 11-05-2016, 05:32 AM   #83
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,622
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Doitsu View Post
@st_albert: I built Sigil using the cutting edge instructions on my Antergos Arch Linux system and ended up with Qt 5.7.0, which works fine.
I.e., you might even be able to use Qt 5.7.0 from the Qt website.
5.7.0 from the Qt website won't have QtWebKit. The last precompiled version that includes QtWebKit is 5.5.1.

I'll have to take look at Sigil's code and see how Qt is involved with launching the plugin via the menu, and how it differs from launching via the plugin button. It almost has to be a QString path getting botched somehow with the former.

If something in Sigil can be changed to work with the repo versions of 5.5.1 (and I have to believe it can, since assigning the plugin to a button still works in the repo version of 5.5.1), then I'd like to find it. They could stay parked on 5.5.1 for quite a while.
DiapDealer is online now   Reply With Quote