To build Sigil on Windows, you need to get/do the following things:
-Sigil is built with VS2017 in the latest versions of Sigil. Begin with making sure you have a working version of Visual Studio, (the free Community edition will work fine).
-The instructions given here will focus on using the command-line cmake and nmake tools. But if you're more comfortable in an IDE, you should find sufficient instructions to get you going. I simply don't use the IDE. Too many fiddly bits (sign-ins and expiring licenses for free software) for my taste. But it did work the last time I tried it.
-From the Start button (you're on your own if you don't have one), go to "All Programs->Visual Studio 2017" and find the command prompt you'll need for your platform. Probably "VS2017 x64 Native Tools Command Prompt" for building a 64-bit package. If you're going to be building 32-bit packages, then use the "VS2017 x86 Native Tools Command Prompt". Create a shortcut to the applicable command-prompt on your Desktop. That's what you'll be using to configure and build Sigil.
-If you're going to use the Visual Studio IDE and cmake-gui, you won't need to use these command-prompts.
+Sigil is built with VS2017 in the latest versions of Sigil. Begin with making sure you have a working version of Visual Studio, (the free Community edition will work fine).
+The instructions given here will focus on using the command-line cmake and nmake tools. But if you're more comfortable in an IDE, you should find sufficient instructions to get you going. I simply don't use the IDE. Too many fiddly bits (sign-ins and expiring licenses for free software) for my taste. But it did work the last time I tried it.
+From the Start button (you're on your own if you don't have one), go to "All Programs->Visual Studio 2017" and find the command prompt you'll need for your platform. Probably "VS2017 x64 Native Tools Command Prompt" for building a 64-bit package. If you're going to be building 32-bit packages, then use the "VS2017 x86 Native Tools Command Prompt". Create a shortcut to the applicable command-prompt on your Desktop. That's what you'll be using to configure and build Sigil.
+If you're going to use the Visual Studio IDE and cmake-gui, you won't need to use these command-prompts.
CMake 3.0 or better is required. I'm using 3.12.x Download it from cmake.org and install it. Make sure CMake's "bin" directory (the one containing "cmake.exe") is added to your PATH.
+CMake 3.0 or better is required. I'm using 3.12.x Download it from cmake.org and install it. Make sure CMake's "bin" directory (the one containing "cmake.exe") is added to your PATH.
Get the unicode version (5.5.9 at the time of this writing) from jrsoftware.org make sure you say yes to the Preprocessor option when installing. Also make sure the Inno Setup directory (the one containing "ISCC.exe") is added to your PATH. There is no 64-bit version of Inno Setup, but you can still use it to create 64-bit program installers.
-Download qt-opensource-windows-x86-5.12.6.exe from Qt's Website and install the msvc2017_64, or msvc2017 component (depending on the architecture you will be building Sigil for). You can install both msvc2017_64 and msvc2017 if you like. Also install the QtWebEngine component.
-If you want to use the exact, patched versions of Qt5.12.6 and QtWebEngine that I've used to release Sigil, feel free to download the whole shebang from my personal repository. It's the archive named: MyQtx64-5.12.6_VS2017_WE.7z (NOTE: you're on your own with a 32-bit version).
-Once you have Qt5.12.6 for Visual Studio installed, make sure its "bin" directory (the one containing "windeployqt.exe) is added to your PATH
+Get the unicode version (5.5.9 at the time of this writing) from jrsoftware.org make sure you say yes to the Preprocessor option when installing. Also make sure the Inno Setup directory (the one containing "ISCC.exe") is added to your PATH. There is no 64-bit version of Inno Setup, but you can still use it to create 64-bit program installers.
+Download qt-opensource-windows-x86-5.12.7.exe from Qt's Website and install the msvc2017_64, or msvc2017 component (depending on the architecture you will be building Sigil for). You can install both msvc2017_64 and msvc2017 if you like. Also install the QtWebEngine component. NOTE: at the time of this writing, Sigil cannot be built with the precompiled version of Qt5.12.7 because of a bug in Qt. Either use Qt5.12.6, or my compiled version of Qt5.12.7 explained below (or compile Qt5.12.7 yourself and patch it with qt5.12.7_windows_qt_add_resources.patch from the Sigil Docs directory).
+If you want to use the exact, patched versions of Qt5.12.7 and QtWebEngine that I've used to release Sigil, feel free to download the whole shebang from my personal repository. It's the archive named: MyQtx64-5.12.7_VS2017_WE.7z (NOTE: you're on your own with a 32-bit version).
+Once you have Qt5.12.7 for Visual Studio installed, make sure its "bin" directory (the one containing "windeployqt.exe) is added to your PATH
This is important. If you're going to be building the 64-bit version of Sigil, you need to install the 64-bit version of Python 3.7. If you're building a 32-bit version of Sigil then you need to install a 32-bit version of Python 3.7.
-The official Windows Sigil installer uses Python 3.7 from Python.org (3.7.2 at the time of this writing). Other flavors of Python may work, but you're on your own if they don't. Download it and install it. If you install somewhere that requires special privileges to add/remove files, you may need to use an administator command prompt to install Sigil's extra Python module dependencies. I recommend installing Python to the default location ($USER/appdata) to avoid that problem. I also recommend allowing the Python installer to add Python to your PATH. This will make it easier for Sigil to locate the necessary Python pieces it needs, and will make it easy to install the extra Python modules using Pythons "pip" tool. I'm going to assume you've done so for the rest of these instructions.
+This is important. If you're going to be building the 64-bit version of Sigil, you need to install the 64-bit version of Python 3.7. If you're building a 32-bit version of Sigil then you need to install a 32-bit version of Python 3.7.
+The official Windows Sigil installer uses Python 3.7 from Python.org (3.7.2 at the time of this writing). Other flavors of Python may work, but you're on your own if they don't. Download it and install it. If you install somewhere that requires special privileges to add/remove files, you may need to use an administator command prompt to install Sigil's extra Python module dependencies. I recommend installing Python to the default location ($USER/appdata) to avoid that problem. I also recommend allowing the Python installer to add Python to your PATH. This will make it easier for Sigil to locate the necessary Python pieces it needs, and will make it easy to install the extra Python modules using Pythons "pip" tool. I'm going to assume you've done so for the rest of these instructions.
After installing Python 3.7, I recommend making sure Python's pip/setuptools is updated to the latest version. The easiest way to do this is to open a command prompt (the shortcut to the VS2015 command prompt you made on your desktop in step 1 will work fine) and type:
-+
python -m pip install -U pipAfter installing Python 3.7, I recommend making sure Python's pip/setuptools is updated to the latest version. The easiest way to do this is to open a command prompt (the shortcut to the VS2015 command prompt you made on your desktop in step 1 will work fine) and type:
++
python -m pip install -U pipOnce finished, you can begin to install the extra modules needed by Sigil.
@@ -45,73 +48,82 @@
-Getting the extra Python module dependencies
- cssselect
- css-parser
- chardet
+- dulwich (0.19.15 recommended/verified) dulwich also requires urllib3 and certifi minimums
- Pillow (v6.2.1 recommended/verified)
- lxml (v4.4.2 recommended/verified)
- PyQt5 (5.12.3 recommended/verified)
-From the same command prompt you updated pip with, install the "six" module with the following command:
-+
pip install sixFrom the same command prompt you updated pip with, install the "six" module with the following command:
++-
pip install sixRepeat for the next five modules:
-+
pip install html5libRepeat for the next six modules:
++
pip install html5libetc...
Installing Pillow
-Other versions of Pillow may work fine, but Sigil's installer build is predicated on v5.4.1, To install that specific version, use the following pip command.
-+
pip install Pillow==6.2.1Other versions of Pillow may work fine, but Sigil's installer build is predicated on v6.2.1, To install that specific version, use the following pip command.
++
pip install Pillow==6.2.1Installing lxml.
-Version 4.3.2 comes with precompiled binary wheels for Windows. Not all versions do. So if you want to install a different version, you'll need to find out if there's precompiled binaries for Windows or not. Install a specific version with pip using the following command
-+
pip install lxml==4.4.2Version 4.4.2 comes with precompiled binary wheels for Windows. Not all versions do. So if you want to install a different version, you'll need to find out if there's precompiled binaries for Windows or not. Install a specific version with pip using the following command
++
pip install lxml==4.4.2Installing PyQt5.
-Like lxml, not all versions of PyQt5 will have compatible binaries that will work with Sigil's Qt5 and Python. Stick to version 5.12.3 and everything should work with Python 3.7 and Qt5.12.6 (the trick is to always select a version of PyQt that will work with Sigil's version of Qt and Python)
-`pip install PyQt5==5.12.3 PyQt5-sip==4.19.18
+Like lxml, not all versions of PyQt5 will have compatible binaries that will work with Sigil's Qt5 and Python. Stick to version 5.12.3 and everything should work with Python 3.7 and Qt5.12.7 (the trick is to always select a version of PyQt that will work with Sigil's version of Qt and Python)
++-`pip install PyQt5==5.12.3 PyQt5-sip==4.19.18
Getting Sigil's Source Code
-You can clone the Sigil Github repository (Requires a Windows git client - I use the portable version from here):
-+
git clone https://github.com/Sigil-Ebook/Sigil.gitGetting Sigil's Source Code
+You can clone the Sigil Github repository (Requires a Windows git client - I use the portable version from here):
++-
git clone https://github.com/Sigil-Ebook/Sigil.gitOr you can download a specific release's zipfile from Sigil's releases page on Github (0.9.10 at the time of this writing).
+Or you can download a specific release's zipfile from Sigil's releases page on Github (1.2.0 at the time of this writing).
I recommend the latter method, as the github repository version might not always be stable at any given moment (even though we try hard not to leave it broken).
-Unzip the source code. Rename the uppermost directory to something useful like "sigil-src". Unless you like typing extra-long directory names in command-prompts--in which case, don't rename it. Remember this location, you'll need it when generating the nmake makefiles with cmake
-Preparing Sigil's Source Code
-To build the Sigil installer package, you'll need to copy the Visual Studio 2017 redistributable runtime installer to the
+<sigil-src>\installerfolder (the one that contains the Sigil.iss file). These redistributable files can usually be found somewhere in Visual Studio's folder structure:Unzip the source code. Rename the uppermost directory to something useful like "sigil-src". Unless you like typing extra-long directory names in command-prompts--in which case, don't rename it. Remember this location, you'll need it when generating the nmake makefiles with cmake
+Preparing Sigil's Source Code
+To build the Sigil installer package, you'll need to copy the Visual Studio 2017 redistributable runtime installer to the
<sigil-src>\installerfolder (the one that contains the Sigil.iss file). These redistributable files can usually be found somewhere in Visual Studio's folder structure:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Redist\MSVC\14.XX.XXXXX\vcredist_x64.exe for 64-bit builds, and vcredist_x86.exe for 32-bit builds.
-The file names are important so don't rename them. Just copy the appropriate one to the "installer" folder in Sigil's source mentioned above.
+The file names are important so don't rename them. Just copy the appropriate one to the "installer" folder in Sigil's source mentioned above.
Configuring and building Sigil (and the Sigil installer package)
Configuring Sigil with cmake
With all the pre-requisites met and all the necessary additions to your PATH, the only thing left to do is generate the Sigil makefiles with cmake.
-Using the shortcut to the proper VSStudio command-prompt created in step 1, cd to a suitable empty directory for building Sigil (I recommend "sigil-build", or some such similar name), and issue the following command:
-+
cmake -G "NMake Makefiles" -DWIN_INSTALLER_USE_64BIT_CRT=1 -DQt5_DIR="C:\Qt\Qt5.12.3\5.12.6\mscv2017_64\lib\cmake\Qt5" -DCMAKE_BUILD_TYPE=Release "C:\path\to\sigil-src"Using the shortcut to the proper VSStudio command-prompt created in step 1, cd to a suitable empty directory for building Sigil (I recommend "sigil-build", or some such similar name), and issue the following command:
++-
cmake -G "NMake Makefiles" -DWIN_INSTALLER_USE_64BIT_CRT=1 -DQt5_DIR="C:\Qt\Qt5.12.7\5.12.7\mscv2017_64\lib\cmake\Qt5" -DCMAKE_BUILD_TYPE=Release "C:\path\to\sigil-src"Leave out the -DWIN_INSTALLER_USE_64BIT_CRT=1 part if you're building a 32-bit version of Sigil with the "VS2017 x86 Native Tools Command Prompt" shortcut.
-Obviously change the paths to match where you've actually installed Qt5.12.6 and the Sigil source code. For instance: using my Specially compiled version of Qt5/WebEngine, it would look like:
--
cmake -G "NMake Makefiles" -DWIN_INSTALLER_USE_64BIT_CRT=1 -DQt5_DIR="C:\MyQtx64_WE\Qt5.12.6\lib\cmake\Qt5" -DCMAKE_BUILD_TYPE=Release "C:\path\to\sigil-src"NOTE: The -DQt5_DIR will be "C:\Qt\Qt5.12.6\5.12.6\mscv2017(_64)\lib\cmake\Qt5" if you installed the standard Qt5.12.6 to its default location
-If this completes successfully, then you're ready to compile Sigil (leave the command prompt open).
+Leave out the -DWIN_INSTALLER_USE_64BIT_CRT=1 part if you're building a 32-bit version of Sigil with the "VS2017 x86 Native Tools Command Prompt" shortcut.
+Obviously change the paths to match where you've actually installed Qt5.12.7 and the Sigil source code. For instance: using my Specially compiled version of Qt5/WebEngine, it would look like:
++
cmake -G "NMake Makefiles" -DWIN_INSTALLER_USE_64BIT_CRT=1 -DQt5_DIR="C:\MyQtx64_WE\Qt5.12.7\lib\cmake\Qt5" -DCMAKE_BUILD_TYPE=Release "C:\path\to\sigil-src"NOTE: The -DQt5_DIR will be "C:\Qt\Qt5.12.7\5.12.7\mscv2017(_64)\lib\cmake\Qt5" if you installed the standard Qt5.12.7 to its default location
+If this completes successfully, then you're ready to compile Sigil (leave the command prompt open).
You can also generate Visual Studio Project/Solution Files with cmake by using:
-+
cmake -G "Visual Studio 14 2017 Win64" WIN_INSTALLER_USE_64BIT_CRT=1 -DQt5_DIR="C:\Qt\Qt5.12.6\5.12.6\mscv2017(_64)\lib\cmake\Qt5" -DCMAKE_BUILD_TYPE=Release "C:\path\to\sigil-src"+-
cmake -G "Visual Studio 15 2017 Win64" WIN_INSTALLER_USE_64BIT_CRT=1 -DQt5_DIR="C:\Qt\Qt5.12.7\5.12.7\mscv2017(_64)\lib\cmake\Qt5" -DCMAKE_BUILD_TYPE=Release "C:\path\to\sigil-src"Leave off "Win64" and -DWIN_INSTALLER_USE_64BIT_CRT=1 if you're building the 32-bit version of Sigil.
-You can also use cmake-gui (double-click on cmake-gui in the cmake/bin directory) and avoid using the command-prompt altogether if you wish (although you're on your own in figuring out how to enter all the cmake configuration options in the gui).
+Leave off "Win64" and -DWIN_INSTALLER_USE_64BIT_CRT=1 if you're building the 32-bit version of Sigil.
+You can also use cmake-gui (double-click on cmake-gui in the cmake/bin directory) and avoid using the command-prompt altogether if you wish (although you're on your own in figuring out how to enter all the cmake configuration options in the gui).
The following three cmake options are used to manually specify which Python3 you want to use when building Sigil instead of relying on the included cmake utilities to try and automatically find a suitable version. They can come in handy it you have multiple versions of Python 3 installed on your computer.
-DPYTHON_LIBRARY=
-<the full path to the python3.x library (ex. python37.lib)>-DPYTHON_INCLUDE_DIR=
+<the path to the directory where python3.x's header files (python.h) can be found>-DPYTHON_INCLUDE_DIR=
<the path to the directory where python3.x's header files (python.h) can be found>-DPYTHON_EXECUTABLE=
-<the full path to the python3.x binary (python.exe)>If you don't want to build/include the bundled Python environment in the Sigil installer, use the -DPKG_SYSTEM_PYTHON=0 in the CMake configure command to disable it. NOTE: you'll have to configure an external Python interpeter for running Sigil plugins. The "Use Bundled Python" feature will be unavailable.
+If you don't want to build/include the bundled Python environment in the Sigil installer, use the -DPKG_SYSTEM_PYTHON=0 in the CMake configure command to disable it. NOTE: you'll have to configure an external Python interpeter for running Sigil plugins. The "Use Bundled Python" feature will be unavailable.
Compiling Sigil
-If you generated NMake Makefiles with cmake (like I do), then compile Sigil by typing
-nmake(at the same command-prompt you just configured with) to begin building Sigil. If it completes without error, you're ready to build the installer package (leave the command prompt open).If you generated Visual Studio 2017 projects/solutions, then open the Sigil.sln file in the build directory; make sure the solution configuration is set to "Release"; select the ALL_BUILD project in the Solution Explorer and build the ALL_BUILD project from the Build menu (Build->Build ALL_BUILD). Note: don't build the solution. If it completes without error, you're ready to build the installer package. It is not possible at this time build a Debug version of Sigil with Visual Studio. So make sure the solution configuration is changed to build "Release" only.
+If you generated NMake Makefiles with cmake (like I do), then compile Sigil by typing
+nmake(at the same command-prompt you just configured with) to begin building Sigil. If it completes without error, you're ready to build the installer package (leave the command prompt open).If you generated Visual Studio 2017 projects/solutions, then open the Sigil.sln file in the build directory; make sure the solution configuration is set to "Release"; select the ALL_BUILD project in the Solution Explorer and build the ALL_BUILD project from the Build menu (Build->Build ALL_BUILD). Note: don't build the solution. If it completes without error, you're ready to build the installer package. It is not possible at this time build a Debug version of Sigil with Visual Studio. So make sure the solution configuration is changed to build "Release" only.
Building the Sigil installer package
-If you generated NMake Makefiles and have successfully compiled Sigil, then type
-nmake makeinstaller(at the same command prompt you just compiled Sigil with) to build the Sigil installer package. If it completes succesfully, the Sigil installer will be placed in the sigil-build directory's "installer" folder (NOTE: that's the build directory and not the source directory). If it doesn't complete succesfully, you may have to delete the "temp_folder" in the build directory before proceeding.If you generated Visual Studio 2017 project/solutions and have built the ALL_BUILD project successfully, then select the "makeinstaller" project in the Solution Explorer and build the makeinstaller project from the Build menu (Build->Build makeinstaller). If it completes succesfully, the Sigil installer will be placed in the sigil-build directory's "installer" folder (NOTE: that's the build directory and not the source directory). If it doesn't complete succesfully, you may have to delete the "temp_folder" in the build directory before proceeding.
+If you generated NMake Makefiles and have successfully compiled Sigil, then type
+nmake makeinstaller(at the same command prompt you just compiled Sigil with) to build the Sigil installer package. If it completes succesfully, the Sigil installer will be placed in the sigil-build directory's "installer" folder (NOTE: that's the build directory and not the source directory). If it doesn't complete succesfully, you may have to delete the "temp_folder" in the build directory before proceeding.If you generated Visual Studio 2017 project/solutions and have built the ALL_BUILD project successfully, then select the "makeinstaller" project in the Solution Explorer and build the makeinstaller project from the Build menu (Build->Build makeinstaller). If it completes succesfully, the Sigil installer will be placed in the sigil-build directory's "installer" folder (NOTE: that's the build directory and not the source directory). If it doesn't complete succesfully, you may have to delete the "temp_folder" in the build directory before proceeding.
Advanced
Environment Variables
The following are environment variables that can be set at runtime to affect how Sigil is run after building/installing.
SIGIL_PREFS_DIR - Changes where sigil looks for and updates its user preference data. Needs to specify a full path in a directory where the user has write privileges.
SIGIL_USES_DARK_MODE=(0|1) - Sigil will use the Windows dark mode setting to determine if it should start in light or darkmode. Should you wish to override this behavior (or enable dark mode on systems that do not have a dark theme), use this variable appropriately.
+ - \ No newline at end of file +