-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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[cuda]] build failure #7913
Comments
|
Release notes for CUDA Tookit (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\CUDA_Toolkit_Release_Notes.txt) are copyrighted, so reluctant to attach. Performed ./vcpkg install opencv[cuda]:x64-windows and it completed with no errors. [Took about 2 hours on 6-core Xeon system - yikes] So, package build needs to be updated to accomodate 10.0+ version of CUDA toolkit. Perhaps continue support for x86-windows pre 10.0, deprecate support after? |
Unfortunately cuda feature is unavailable with x86 triplets, only x64 ones work. |
Host Environment
To Reproduce
Steps to reproduce the behavior:
./vcpkg install opencv[cuda]
Failure logs
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:58 (message):
Command failed: ninja -v
Working Directory: C:/DevTools/Development/Tools/Microsoft/vcpkg-2019-08-26/buildtrees/opencv4/x86-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
C:\DevTools\Development\Tools\Microsoft\vcpkg-2019-08-26\buildtrees\opencv4\config-x86-windows-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:296 (vcpkg_execute_required_process)
ports/opencv4/portfile.cmake:244 (vcpkg_configure_cmake)
scripts/ports.cmake:85 (include)
Error: Building package opencv4:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with
.\vcpkg update
, thensubmit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: opencv4:x86-windows
Vcpkg version: 2019.08.16-nohash
Additional context
config-x86-windows-out.log
The text was updated successfully, but these errors were encountered: