This PR introduces a fix for building DALI Backend directly within Triton container with -D TRITON_SKIP_DALI_DOWNLOAD=ON option passed to the cmake.
When the aforementioned option is passed to cmake, get_dali_paths function is responsible for discovering the path of the DALI installation in the system. This function uses DALI and Python directly. In case of building within Triton container, the system-defined python path is not the proper one. The proper python path is the one created by the conda environment, which has a different path than the system-defined python binary. This PR allows to specify which python should be used inside get_dali_paths invocation.
From now on, when DALI is built within Triton docker container, TRITON_DALI_BUILD_IN_TRITON option shall be turned ON (it is not the default option).
This PR introduces a fix for building DALI Backend directly within Triton container with
-D TRITON_SKIP_DALI_DOWNLOAD=ON
option passed to the cmake.When the aforementioned option is passed to
cmake
,get_dali_paths
function is responsible for discovering the path of the DALI installation in the system. This function uses DALI and Python directly. In case of building within Triton container, the system-definedpython
path is not the proper one. The properpython
path is the one created by the conda environment, which has a different path than the system-definedpython
binary. This PR allows to specify whichpython
should be used insideget_dali_paths
invocation.From now on, when DALI is built within Triton docker container,
TRITON_DALI_BUILD_IN_TRITON
option shall be turnedON
(it is not the default option).