Sigil and calibre Open With - Page 2

DiapDealer · 10-05-2025, 12:10 PM

This may be unavoidable without jumping through a ton of hoops. The version of Chromium in QtWebEngine 6.9.x requires Windows 11 SDK version 10.0.26100.0, which was not introduced until Visual Studio 17.10.

DiapDealer · 10-05-2025, 01:09 PM

Ok, it was fairly trivial to install Visual Studio 17.8 and then add the Windows 11 (26100) SDK using winget. I'm running a test build of Qt6.9.3 now, so we'll see how things go. Fingers crossed!

DNSB · 10-05-2025, 07:33 PM

In my testing with compiling calibre and checking various VC runtimes, trying to use open with with VCredist 14.38.33130.0 or higher worked. The 14.36 version despite using the patched version of calibre which should not have passed the link to calibre's internal install of the VC dlls did not work.

DiapDealer · 10-05-2025, 08:14 PM

I have built Sigil (with Visual Studio 7.9.5) using a patched version of Qt6.9.3 (built with Visual Studio 17.8). I hope to test it on a work laptop tomorrow to see if it will work with Calibre's inherent Open With (before Kovid's recent changes and eventually after), and runtimes earlier than version 14.40.

DiapDealer · 10-06-2025, 11:05 AM

My test version of Sigil (built entirely with versions of Visual Studio earlier than 17.10), works fine with the 8.11 Calibre Open With (and its msvcp140.dll v14.36) and works fine with any of the pre 14.40 runtimes I've tested it with.

There may come a time when an official release of Sigil will need to break binary compatibility with older Visual Studio 2015-2022 VC++ runtimes, but it is not THIS day.

This means that GitHub CI builds of Sigil might (or might not; we'll see) need Post-14.40 Visual Studio 2015-2022 VC++ runtimes to work (and might not work with Calibre's Open With), but there's little to do about that.

DiapDealer · 10-06-2025, 11:45 AM

Actually it looks like CI versions of Sigil built with the latest Visual Studio versions will still work without breaking backward binary compatibility. I only need to make sure that Qt6.9 is built with pre-17.10 to keep things compatible.

Those who build their own Sigil can use the latest Visual Studio to build Sigil, but need to use my CI ready pre-compiled Qt6.9.3 if they want to keep Sigil as compatible as possible. It can be found in the usual spot where my CI scripts grab it from.

10-05-2025, 07:33 PM	#18
DNSB Bibliophagist Posts: 47,846 Karma: 174304428 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	In my testing with compiling calibre and checking various VC runtimes, trying to use open with with VCredist 14.38.33130.0 or higher worked. The 14.36 version despite using the patched version of calibre which should not have passed the link to calibre's internal install of the VC dlls did not work. Last edited by DNSB; 10-05-2025 at 07:42 PM. Reason: correct past to passed

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Sigil Error Message: Book File Would Not Open in Sigil	fkustaa	Sigil	9	04-27-2025 05:11 AM
Calibre cannot open ebook reader, edit books, or re-open once closed	baggins41	Calibre	15	04-22-2021 07:54 AM
New message when I open Sigil 0.9.17	dynabook	Sigil	23	08-19-2019 08:07 PM
Sigil don't open	winky8	Sigil	8	12-11-2013 07:15 PM
"PK": Only text when I open in Sigil an ePub file generated with Calibre	Terisa de morgan	Sigil	3	12-14-2009 11:24 AM

10-05-2025, 12:10 PM	#16
DiapDealer Grand Sorcerer Posts: 28,836 Karma: 207000000 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	This may be unavoidable without jumping through a ton of hoops. The version of Chromium in QtWebEngine 6.9.x requires Windows 11 SDK version 10.0.26100.0, which was not introduced until Visual Studio 17.10.

10-05-2025, 01:09 PM	#17
DiapDealer Grand Sorcerer Posts: 28,836 Karma: 207000000 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Ok, it was fairly trivial to install Visual Studio 17.8 and then add the Windows 11 (26100) SDK using winget. I'm running a test build of Qt6.9.3 now, so we'll see how things go. Fingers crossed!

10-05-2025, 08:14 PM	#19
DiapDealer Grand Sorcerer Posts: 28,836 Karma: 207000000 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I have built Sigil (with Visual Studio 7.9.5) using a patched version of Qt6.9.3 (built with Visual Studio 17.8). I hope to test it on a work laptop tomorrow to see if it will work with Calibre's inherent Open With (before Kovid's recent changes and eventually after), and runtimes earlier than version 14.40.

10-06-2025, 11:05 AM	#20
DiapDealer Grand Sorcerer Posts: 28,836 Karma: 207000000 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	My test version of Sigil (built entirely with versions of Visual Studio earlier than 17.10), works fine with the 8.11 Calibre Open With (and its msvcp140.dll v14.36) and works fine with any of the pre 14.40 runtimes I've tested it with. There may come a time when an official release of Sigil will need to break binary compatibility with older Visual Studio 2015-2022 VC++ runtimes, but it is not THIS day. This means that GitHub CI builds of Sigil might (or might not; we'll see) need Post-14.40 Visual Studio 2015-2022 VC++ runtimes to work (and might not work with Calibre's Open With), but there's little to do about that.

10-06-2025, 11:45 AM	#21
DiapDealer Grand Sorcerer Posts: 28,836 Karma: 207000000 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Actually it looks like CI versions of Sigil built with the latest Visual Studio versions will still work without breaking backward binary compatibility. I only need to make sure that Qt6.9 is built with pre-17.10 to keep things compatible. Those who build their own Sigil can use the latest Visual Studio to build Sigil, but need to use my CI ready pre-compiled Qt6.9.3 if they want to keep Sigil as compatible as possible. It can be found in the usual spot where my CI scripts grab it from.

Advert

Advert