@raymondEhlers : there are two possibilities, either:
- we let cmake automatically infer the alternative pyenv python installation by doing:
```
file( GLOB PY_ALT_PREFIX_PATH "$ENV{PYENV_ROOT}/versions/${XRD_PYTHON_REQ_VERSION}*" )
set( CMAKE_PREFIX_PATH "${CMAKE_PREFIX_PATH};${PY_ALT_PREFIX_PATH}" )
```
The advantage is you don't need to do anything it should work out of the box, the disadvantage is that if there are more than one installations say `3.9.1` and `3.9.2` cmake will make an arbitrary choice for you.
- we let you specify an environment variable, say `XRD_PY_PREFIX_PATH` and then in the cmake:
```
set( CMAKE_PREFIX_PATH "${CMAKE_PREFIX_PATH};$ENV{XRD_PY_PREFIX_PATH}" )
```
The advantage is you are in control, the disadvantage is it is not automatic.
Let me know your thoughts!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/1474#issuecomment-904545769
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
