Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[opencv] vcpkg doesn't read CUDA_ARCH_BIN and CUDA_ARCH_PTX env vars #42794

Open
nvandamme opened this issue Dec 19, 2024 · 0 comments
Open

[opencv] vcpkg doesn't read CUDA_ARCH_BIN and CUDA_ARCH_PTX env vars #42794

nvandamme opened this issue Dec 19, 2024 · 0 comments
Assignees
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist

Comments

@nvandamme
Copy link

nvandamme commented Dec 19, 2024

Is your feature request related to a problem? Please describe.

Opencv use two env vars to force specific CUDA archs and PTX version before compiling.

The actual port compile for every CUDA archs (up to 90+ gen, even if the system report a specific gen code) and thus take a very long compile time.

Using VCPKG_KEEP_ENV_VARS=CUDA_ARCH_BIN;CUDA_ARCH_PTX as a registered env var doesn't solve this issue.

Proposed solution

  • read CUDA_ARCH_BIN and CUDA_ARCH_PTX env vars and set CUDA gen and ptx familly code accordingly on configure.
  • modify CMake CUDA system detect to compile for the detected arch/ptx version of the current system only by default.
  • OR provide a switch or an env var to force CUDA setup to match only system installed cards archs/ptx famillies

Describe alternatives you've considered

No response

Additional context

No response

@nvandamme nvandamme added the category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist label Dec 19, 2024
@nvandamme nvandamme changed the title [opencv] vcpkg doesn't read CUDA_ARCH_BIN and CUDA_AARCH_PTX env vars [opencv] vcpkg doesn't read CUDA_ARCH_BIN and CUDA_ARCH_PTX env vars Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist
Projects
None yet
Development

No branches or pull requests

2 participants