ATTN: Windows Sigil users

[DiapDealer]

If you want, I have two test builds for the latest Sigil (with Qt6.9.2) avialable here: https://github.com/dougmassay/win-qt...s/tag/v5.212-1

They're the usual Sigil installers. "Test" was built locally by me with an older version of Visual Studio, and "Test2" was built with the latest Visual Studio by the Github CI process.

See if you have any trouble running either of those. You have a newer redist installed, so that shouldn't be a factor for either one.

[BeckyEbook]

I confirm that both of your versions (test and test2) work fine.
For me, it's only worse... Now it has completely stopped building, so I'll probably have to "plow" everything and reinstall all the components necessary to build Sigil.

We already know for sure that it's something on my end, since it works for you.

Thanks, I'll think about it and keep trying.

I would be happy to receive, via PM, a detailed build log, for example, because I might find something strange there, as well as the CMake version (I previously used 3.29.2 with Strawberry, but now I have installed the latest version: 4.1.1) and other details that might be useful to me. I have the recommended Python 3.13.2.

[DNSB]

For what it may be worth, I built Sigil with Qt 6.9.2 using the August update to Visual Studio 2022 and it installed and ran. I'm now updating to the September release of VS 2022 and will rebuild and see if any issues show. I'm still using the old CMake 3.30.8 but will update to 4.1.1 to see if it makes any difference.

• Windows 11 Pro 24H2
• Visual Studio 2022 17.14.15 (September 2025)
• VCTools 14.44.35207
• VCRedist 14.44.35211

Edit: Both versions (with the old CMake and new CMake) compiled, installed and opened happily.

One quick question: I've been removing the Sigil-master directory and replacing it with a new extract from the downloaded zip file to give a clean environment. Is that actually necessary with Sigil?

I can't do much testing since my youngest granddaughter has woken up and needs attention.

[BeckyEbook]

For those interested:
I did it!
I uninstalled VS2022 and reinstalled it
CMake 4.1.1 (newest)
Inno Setup 6.5.3 (newest)
Python 3.13.2
Of course, Qt 6.9.2.

Sigil builds and runs nicely. Indirect proof of this is that the SVG_Filter_Test.epub file works – I can see the red color in the graphics.

[KevinH]

Glad to hear it!

Originally Posted by BeckyEbook

For those interested:
I did it!
I uninstalled VS2022 and reinstalled it
CMake 4.1.1 (newest)
Inno Setup 6.5.3 (newest)
Python 3.13.2
Of course, Qt 6.9.2.

Sigil builds and runs nicely. Indirect proof of this is that the SVG_Filter_Test.epub file works – I can see the red color in the graphics.

Attachment 218140

[DiapDealer]

Originally Posted by DNSB

One quick question: I've been removing the Sigil-master directory and replacing it with a new extract from the downloaded zip file to give a clean environment. Is that actually necessary with Sigil?

Sorry, I missed this earlier. No, that's not really necessary so long as your build directory is removed. The source tree should remain untouched during the process (unless, of course, your build directory is inside the source tree somewhere--but even that can be safely emptied before another build with no problem.

You may miss a commit to the source tree if you don't redownload it, but that's another story.

[DiapDealer]

I'll probably avoid jumping to the very latest Inno Setup version for the release version of Sigil for a bit. When I jumped to 6.4 too early, one of the various Windows repository's tools could not extract the contents of Sigil's installer. I learned to stay a bit behind on this just in case. No problem at all updating to the very latest for personal builds, though!

Here was the issue with ScoopInstaller and Inno 6.4 for any interested: https://github.com/ScoopInstaller/Extras/issues/14717

[BeckyEbook]

Oh! I didn't even notice that, but I admit that maintaining compatibility with Innounp is useful. The changes in the latest version are not very significant for the Sigil installer, because most of the advanced features of Inno Setup are not used. Only the upcoming version 6.6 will change the appearance to something more like Windows 11, but the key thing is the installation, not admiring the appearance of the installer

[DiapDealer]

We need a minimum of 6.3.3 (I think) to allow installation on Windows arm64. I'm up to 6.4 for Sigil releases. I think I saw that the forked version of innounp that ScoopInstall uses was good up to Inno Setup 6.5.3.