|
I still hope to be able to pull many of the latest bugfixes into a new Windows Legacy release of Sigil sometime soon. But I'm afraid it's always going to be an "as is" release. Caveat emptor if you will.
Too much of Sigil's code (and the code of its dependencies) requires C++11 compliance which means that Visual Studio 2015 is fastly becoming a minimum requirement for compiling Sigil (and its dependencies) on Windows (which doesn't automatically disqualify XP, but Python 3.5+--which is built with VS2015--IS incompatible with XP which means a legacy Sigil will have to be backported to use Python 3.4).
The new community version of QtWebKit we'd like to use moving forward requires vs2015 and Windows 7 at a minimum. The precompiled binary versions of Qt5 that I may be able to start using again to build Windows Sigil releases (which would make my life so, so much easier) would leave both XP and Vista behind (with regard to Sigil compatibility).
So if I can cobble together something that uses Qt5.6 and Python 3.4 that will provide all the features and bugfixes of Sigil's latest code-base using vs2013 (or vs2015 if that proves impossible), then I will. But it will go largely unsupported, and it will likely be the last of its kind, unfortunately.
|