View Single Post
Old 12-22-2024, 08:36 PM   #2
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,701
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I made it easier, but not simple. The first step is configuring the build using a cmake Visual Studio generator (rather than the NMake Makefiles generator).

The bottom line is that I made easier for me to debug Sigil on Windows using the IDE.

It's still quite involved and largely undocumented. Maybe I'll get around to documenting it sometime in the new year. But if you don't have an urgent need to do any Sigil debugging using the Visual Studio IDE. I don't really recommend tackling it. I only do it to get stack traces when investigating crashes. Something we were never really able to easily accomplish on Windows before. I haven't heard of any reliably repeatable Sigil crashes on Windows lately.

And no... debugging with the VS IDE does not involve any settings from within Sigil. So while it's definitely not a user feature, as such; neither is it a bug fix.

Last edited by DiapDealer; 12-23-2024 at 07:39 AM.
DiapDealer is online now   Reply With Quote