Quote:
Originally Posted by DNSB
Tried the font metrics and looks like it works.
One other quick question, I compiled Sigil 2.30 under Windows and had to modify the original command line I used a while back (2.1.0???) since 2.3.0 insisted on finding the Python.exe installed with 2.3.0 as the executable so I had to force the Python install location. Is this expected?
Code:
-DTRY_NEWER_FINDPYTHON3=1
-DPython3_LIBRARIES="%localappdata%\Programs\Python\Python311\libs\"
-DPython3_INCLUDE_DIRS="%localappdata%\Programs\Python\Python311\include"
-DPython3_EXECUTABLE="%localappdata%\Programs\Python\Python311\"
Edit: The reason for compiling Sigil 2.3.0 was to check out the fix for the double popups. I haven't seen one in opening ~20 ePubs so looks good. |
That used to happen to me in the past. Not sure what triggers it, actually (perhaps Sigil was actually running in memory during the build?). I've been manually specifying the Python3 components (as you did) for years. I'm pretty sure Python3_EXECUTABLE needs to point to the actual binary, though.