conda-forge / conda-forge/conda-forge.github.io

How to handle which version install by default in CUDA-enabled recipe?

Abierto
#1,978 1 comentario 0 reacciones 0 asignados Ver en GitHub
question
Lenguaje dominante
JavaScript
Estrellas
170
Forks
320
Merge medio
2 d 10 h
PR fusionados (30 d)
5

Descripción

### Your question:

Hello, I recently worked on CUDA-enabled recipes (mainly https://github.com/conda-forge/librealsense-feedstock and https://github.com/conda-forge/onnxruntime-feedstock/pull/63) and I have two doubts that I was not able to find the answer to by looking at existing feedstocks and documentation.

The questions are:

* Q1: If a feedstock produces both CPU and CUDA enabled builds, which one should be installed by default? I guess possible answers are:
* A: CPU build should be installed by default
* B: CUDA build should be installed by default
* C: Each feedstock should decide on its own, as the trade-off are different for each feedstock

* Q2: Once it is decided which version is installed by default, how it should be marked which version is the one with the highest priority that should be installed by default?
* A: Increase the build number of the preferred version, as done by jaxlib (https://github.com/conda-forge/jaxlib-feedstock/blob/46a1829880e7012e9a05bf8904ddbbc9e5e51375/recipe/meta.yaml#L5)
* B: Use track_features, as done by libarrow (https://github.com/conda-forge/arrow-cpp-feedstock/blob/e5a31a003a2f11bdf72b3e9e2d90f95691aa5f6a/recipe/meta.yaml#L78) and tensorflow (https://github.com/conda-forge/tensorflow-feedstock/blob/2fdde9bd0977c9356ad192d684c8ca2751bf94ab/recipe/meta.yaml#L129)
* C: Use both an increase build number and track_features, as done by pytorch (https://github.com/conda-forge/pytorch-cpu-feedstock/blob/main/recipe/meta.yaml)

Thanks a lot in advance for any hint on this!

fyi @conda-forge/help-c-cpp @conda-forge/cuda-version @conda-forge/jaxlib @conda-forge/pytorch-cpu @conda-forge/arrow-cpp @conda-forge/tensorflow

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.