No problem.
The main reason you have to build and run the Sigil installer after making changes is that by default, Sigil on Windows relies on the bundled Python paths for all of it's embedded Python needs. If Python is not where Sigil thinks it's supposed to be, things break.
But if you're doing development that doesn't involve any embedded Python work or any plugin framework stuff, you can always add -DPKG_SYSTEM_PYTHON=0 to the initial cmake configuration command. That way, so long as the necessary Python installation and the Qt libraries are on the system path, Sigil should be able to be run from the build folder (without installing it). And should you consequently build the installer, Python will not be bundled with Sigil -- but can still make use of the system python for the necessary embedded python requirements (and can still run plugins so long as an external python interpreter is configured).
|