[FEA]: Improve handling of CUDA_HOME and CUDA_PATH in build across projects #1433

Activity

1. github-actions

   added

   triageNeeds the team's attentionNeeds the team's attention

   on Jan 6, 2026
2. Andy-Jost

   added

   P2Low priority - Nice to haveLow priority - Nice to have

   cuda.pathfinderEverything related to the cuda.pathfinder moduleEverything related to the cuda.pathfinder module

   and removed

   triageNeeds the team's attentionNeeds the team's attention

   on Jan 6, 2026
3. Andy-Jost

   added the

   Task

   issue type on Jan 6, 2026
4. Andy-Jost

   removed the

   Task

   issue type on Jan 7, 2026
5. rparolin

   added this to the cuda.pathfinder 1.4.0 milestone on Jan 8, 2026
6. rparolin

   assigned

   rwgk

   on Feb 6, 2026
7. rwgk

   added

   P1Medium priority - Should doMedium priority - Should do

   and removed

   P2Low priority - Nice to haveLow priority - Nice to have

   on Mar 4, 2026
8. rwgk

   removed this from the cuda.pathfinder 1.4.0 milestone on Mar 4, 2026
9. rparolin

   added this to the cuda.core v0.7.0 milestone on Mar 10, 2026
10. rwgk

    added

    P0High priority - Must do!High priority - Must do!

    and removed

    P1Medium priority - Should doMedium priority - Should do

    on Mar 17, 2026
11. rwgk commented on Mar 20, 2026

    

    rwgk

    on Mar 20, 2026

    Contributor

    More actions

    Reminder: Once cuda-pathfinder 1.5.0 (anticipated version) with the centralized CUDA_PATH/CUDA_HOME handling from this issue is released, we should pin the cuda-pathfinder dependency in both cuda_bindings and cuda_core to >=1.5 (published packages on PyPI/conda-forge). Without that lower bound the solver won't prevent pairing older pathfinder versions with bindings/core that import from the new env_vars module, leading to runtime errors.
12. cpcloud

    closed this as completedin #1801on Mar 24, 2026