Re: [wsjt-devel] WSJT-X: User Guide built with CMake - was: Re: WSJT-X: User Guide updates for v1.5.0

[Bill S. <g4...@cl...>]

On 29/04/2015 00:52, KI7MT wrote:
> Hi Bill,
<snip>
>
>> I suppose I could invoke asciidoc like:
>>
>>      ${PYTHON_EXE} ${ASCIIDOC} ....
>>
>> which would bypass the shebang/Windows file associations and allow the
>> location of Python to be set by the CMake finder, that way you could
>> steer the version of Python from CMAKE_PREFIX_PATH.
> There is some good news here. Makefiles process things one line at a
> time, and in their own shell.
>
> So, if there is a var set for the path to python2, then $(PYTHON)
> $ASCIIDOC) x,y,z should only use the Python2 interrupter. Likewise, if
> the var is set to Python3, it should work for 3 only.
I'm not sure of the relevance of any of that?

I have changed the WSJT-X CMake script to use find_package() to locate 
the Python interpreter and have made it an error if a v3 or newer one is 
found. I have also executed asciidoc explicitly using the interpreter 
found above. This will allow multiple Python interpreters even if the v3 
is first on the PATH or associated with .py files on Windows, all you 
need to do is set the correct Python directory in your CMAKE_PREFIX_PATH 
if you happen to have a Python v3 on the path ahead of any earlier version.
>
>
> <snip>
>
> 73's
> Greg, KI7MT
73
Bill
G4WJS.