Quote:
Originally Posted by DiapDealer
No. RepoLog has nothing to do with debug logging. On Windows, create an environment variable named SIGIL_DEBUG_LOGFILE and set it to a path (including the file name itself) where you want debug output to be printed. Then use Qt's qDebug() function to output stuff. There's plenty of examples in Sigil's code. Microsoft makes it nearly impossible to get any console logging happening from a Qt gui application. But I hear some people have luck getting a cygwin/bash prompt to show the stdout/stderr of a running program.
The answer to your previous question is "it depends." If you've changed nothing in any of Sigil's libraries and support files then you might be able to get by with replacing just the Sigil binary. I play it safe, myself. I find the time it takes to install sigil is trivial compared to the painfulness of configuring/compiling Sigil on Windows.
|
Thanks, this really helps.
By the way, I find the Building_Sigil_on_Windows.md having some bugs in building 1.1.0. I get everything well before 'nmake makeinstaller' but in 'nmake makeinstaller' I get error result in the end.
[100%] Copying installer files to temporary location...
Warning: Unable to read C:\MyQtx64_WE\Qt5.12.6\mkspecs\qconfig.pri: NMAKE : fatal error U1077: “D:\MyQtx64_WE\Qt5.12.6\bin\windeployqt.exe”: return code “0x1”
Stop.
NMAKE : fatal error U1077: “"D:\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bi n\HostX64\x64\nmake.exe"”: return code “0x2”
And I use the D:\MyQtx64_WE\Qt5.12.6\mkspecs\qconfig.pri, not C:\
Do you know what happened?