Quote:
Originally Posted by DiapDealer
I never really heard much more about it, to tell the truth. I couldn't tell from the old thread whether those repo versions that were having the problem used Qt5.5.1. Does that version come stock with Xenial? If so, it's definitely worth looking into. I've never had any problems building Sigil against the repo versions of Qt5.6/7 on Arch, so it's possible there's something about 5.5.1.
|
Xenial comes with Qt 5.5.1 out of the box. On another Xenial machine, I built Sigil 0.9.6 with Qt 5.5.1 from the official QT website, and it has no problems. When I get time, I'll try building 0.9.7 on that machine with the "official" Qt 5.5.1 and see what happens. I'll be surprised if it doesn't work.
ETA: Yep, it does work. So there's nothing intrinsically wrong with Qt 5.5.1 with respect to Sigil.
It's probably beating a dead horse, but perhaps I'll install the extra -dev packages and build it per the "cutting edge linux" method (i.e. with all the repo-built Qt components) and if it has the bug, that'll be interesting. Prediction: I bet it does.
... and... yes, the same error occurs. Therefore I conclude that when Sigil is built with the repo-supplied Qt 5.5.1 the bug will appear, but if built with Qt 5.5.1 installed from the Qt website, it does not exhibit that bug. BTW, even with the buggy sigil, I can still execute the plugin via the plugin button. Same situation as in the older thread mentioned above.