Quote:
Originally Posted by DiapDealer
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 (perhaps Python3_LIBRARIES as well).
|
Thanks for the information. Interesting oddment: When I added python.exe to the end of the executable item, I had to remove the "s around the entry or the source directory was not seen. It didn't seem to make any difference to the compile cycle whether I had python.exe at the end of the item or not.